Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Compiled EXE still looking for objects in vcx files.
Message
General information
Forum:
Visual FoxPro
Category:
Project manager
Miscellaneous
Thread ID:
00454439
Message ID:
00454473
Views:
22
>>>>>>>>>>>
I've compiled a project into a standalone EXE and installed everything it needs onto a different machine. When running the EXE, I get the following:

"Error instantiating class. Cannot find c:\vpetradev\libs\abizness.vcx"

Why would a compiled exe still be looking for source code in the original development directory? Any ideas why a standalone EXE needs to access the source code in order to function?

FWIW, a previous version of this system using local VFP tables didn't exhibit this problem, but it is now switched to remote views accessing a SQL 7 backend. Just in case that's worth anything.

TIA
>>>>>>>>>>>>>>>
I've found that even though I included the libraries in the EXE, I still need to create an empty directory called "libs" in the appropriate place. I think Foxpro first looks there for the lib and if it does'nt find it it looks within the EXE. But if the directory does'nt exist it stop there and gives you an error. At least this solution works for me.
Previous
Reply
Map
View

Click here to load this message in the networking platform