Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Size of 'run window'
Message
From
01/06/2004 21:48:52
Dragan Nedeljkovich (Online)
Now officially retired
Zrenjanin, Serbia
 
General information
Forum:
Visual FoxPro
Category:
Coding, syntax & commands
Miscellaneous
Thread ID:
00908233
Message ID:
00909124
Views:
10
>Dragan,
>
>In house, all the VCX are in a subdirectory that is * not * included in the search path. They are included (as mentioned) in the setclasslib statement.
>Normally, I run a program such as startup.prg (as opposed to .app or .exe)
>
>In the field, the VCX are included in the project a .exe is run.
>
>In keeping with the above set-up, what are you recommendations?

Well, check that process.vcx is really there - suspend immediately after your set classlib statement, and try to instantiate the class from the command window. Instead of your batch file, you can use any DOS command ("Dir >tmp.txt" would do), and use "NOR" instead of "HID" as the last parameter while testing, so you get to see your DOS window.

If it works there but not in the piece of code where you really want to use it, check whether Set("Classlib") still keeps process.vcx - you may have a piece of framework code which sticks to some previously created list (I know I've had this problem elsewhere).

If this is not working - try CreateObject instead of NewObject(), or try mentioning process.vcx with a path. Newobject() may well ignore the Set Classlib (didn't test that, ever), and without a path, it wouldn't be able to find it then.

back to same old

the first online autobiography, unfinished by design
What, me reckless? I'm full of recks!
Balkans, eh? Count them.
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform