Hi everyone,
I've been developing a Client/Server frontend based on VFP 6.0. and mySQL as backend for a real state company down here in Mexico.
Initially, I started developing in my office, setting up the whole environment there. When I released the first beta version of the .EXE file, I sent it to my client (who's using VFP 6.0 also on a Windows 2003 Server) and everything ran Ok.
Trying to speed up things, I moved my source code to my client's platform (stated above) and continued debugging and developing new modules.
After a while, I tried to create a final .EXE file. It was generated ok but when I doubled click its icon, I received a message: "XYZ.EXE not a valid Win32 application".
I have checked that recompiling my .EXE in other platform (let's say, Win XP in other PC) and porting this .EXE file to the file server, stops sending this message.
As far as I know, a few weeks ago this server failed to install a service pack due to lack of space. My customer's IT area is working on this issue right now. I mention this because I'm using some MS ActiveX controls (i.e. Progress Bar and StatusBar Controls v.6.0).
So, I've found this workaround, but it's really annoying. Could it be that this failed service pack is the root cause of my issue? Is there another reason? BTW another clue: smaller (dummy) .EXE files compile and work fine!!!
Thanks for any suggestion or idea.
Take away all the buzz of this biz and what do you get? 01000100101010...
I've been developing a Client/Server frontend based on VFP 6.0. and mySQL as backend for a real state company down here in Mexico.
Initially, I started developing in my office, setting up the whole environment there. When I released the first beta version of the .EXE file, I sent it to my client (who's using VFP 6.0 also on a Windows 2003 Server) and everything ran Ok.
Trying to speed up things, I moved my source code to my client's platform (stated above) and continued debugging and developing new modules.
After a while, I tried to create a final .EXE file. It was generated ok but when I doubled click its icon, I received a message: "XYZ.EXE not a valid Win32 application".
I have checked that recompiling my .EXE in other platform (let's say, Win XP in other PC) and porting this .EXE file to the file server, stops sending this message.
As far as I know, a few weeks ago this server failed to install a service pack due to lack of space. My customer's IT area is working on this issue right now. I mention this because I'm using some MS ActiveX controls (i.e. Progress Bar and StatusBar Controls v.6.0).
So, I've found this workaround, but it's really annoying. Could it be that this failed service pack is the root cause of my issue? Is there another reason? BTW another clue: smaller (dummy) .EXE files compile and work fine!!!
Thanks for any suggestion or idea.
Take away all the buzz of this biz and what do you get? 01000100101010...
