More "Package and Deploy" Trouble
and I am running into an error "The procedure entry point SetWifdowOrgEx could not be located in the dymanic link library GDI32.DLL. ??
I have already replaced the file on the New Machine in the "Windows\System32 dir. to no avail, App Built on XP Pro platform and I am Installing on a Vista Basic Machin3e if that possibly is relevant info - any help will be appreciated .
Thanx
[386 byte] By [
mbhey101] at [2007-11-20 11:47:37]
# 1 Re: More "Package and Deploy" Trouble
Do you get this error while creating the setup project, or while installing your program onto a client
# 2 Re: More "Package and Deploy" Trouble
Er... is it really SetWifdowOrgEx or is this a typo, being SetWindowOrgEx.
WoF at 2007-11-9 19:33:23 >
# 3 Re: More "Package and Deploy" Trouble
Do you get this error while creating the setup project, or while installing your program onto a client
Installing onto a client
# 4 Re: More "Package and Deploy" Trouble
Er... is it really SetWifdowOrgEx or is this a typo, being SetWindowOrgEx.
No Typo - spelling is correct.
# 5 Re: More "Package and Deploy" Trouble
I was able to get by the "SetWifdowOrgEx" from an earlier Thread - How? - Don't ask me. - However I have 2 other issues I'm now faced with:
1. During the Install (On the Client - which is a Vista Basic Edition) the file "c:\windows\system32\catsrv.dll" fails to register - this file is newer on the Vista (Client) then the Package and Deploy Wizard bundles up from the XP machine to install on client (just left the newer file on the client). When I try to register "catsrv.dll" manually from the "Run Box" I get this error that the file was loaded but the call to "DllRegisterServer" failed with error code 0a80029c4a. I don't know how critical this issue is.
2. When I try to launch my APP on the Client - after Install this error appears:
"Run Time Error '432' - Filename or classname not found during Automation operation." I am much more concerned about this issue since I still cannot run my APP on the Client.
Any help would be appreciated.
====================================================
The above error (2) was my oversight - I forgot to copy a .udl file that I needed for database filepath. - However if you could enlighted me on why the catsrv.dll was unable to register - that would be fine.
# 6 Re: More "Package and Deploy" Trouble
GDI32.dll does only contain a SetWindowOrgEx function, so SetWifdowEx could not work at all. But this must already reveal at compile time...
WoF at 2007-11-9 19:37:35 >
# 7 Re: More "Package and Deploy" Trouble
This issue resolved itself - for some reason - I appreciate the info though.
# 8 Re: More "Package and Deploy" Trouble
There is absolutely no, I repeat, no SetWifdowOrgEx function. Full Stop. There is only a SetWindowOrgEx function ( as pointed out by WoF ), which which logical point maps to the device point. Read here :
http://msdn2.microsoft.com/en-us/library/ms533192.aspx
You say the spelling is correct, the only way I can perhaps see why your VB compiler doesn't pick it up, is beacuse you haven't used Option Explicit in your code; which forces all variables to be declared, and if there is a typo, such as this one, it would pick it up.
# 9 Re: More "Package and Deploy" Trouble
[ Merged Thread ]
# 10 Re: More "Package and Deploy" Trouble
It seems if you have misspelled a function name in a declare statement, the compiler checks only when fully compiling or in the IDE when executing the statement where used.
Unfortunately Option Explicit doesn't help here.
WoF at 2007-11-9 19:41:39 >
# 11 Re: More "Package and Deploy" Trouble
There is absolutely no, I repeat, no SetWifdowOrgEx function. Full Stop. There is only a SetWindowOrgEx function ( as pointed out by WoF ), which which logical point maps to the device point. Read here :
http://msdn2.microsoft.com/en-us/library/ms533192.aspx
You say the spelling is correct, the only way I can perhaps see why your VB compiler doesn't pick it up, is beacuse you haven't used Option Explicit in your code; which forces all variables to be declared, and if there is a typo, such as this one, it would pick it up.
This was the error I received - "Which I am absolutely 100% sure of" - I verifed the spelling 3 times - all of a sudden my Install did not pop up with this error anymore - Why I don't know. Also, there is no variable "SetWifdowOrgEx" anywhere in my code - so there is no typo period. SO THERE!!!!!!!!!!!!!!
