Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Are there VFP commands that cannot be in a DLL?
Message
General information
Forum:
Visual FoxPro
Category:
Client/server
Miscellaneous
Thread ID:
00105788
Message ID:
00105827
Views:
56
Dave,

Thanks.....yup, even though the database was closed, I had the project open. Once I closed the project, the database opened just fine. And thanks again, I had to remember that this was going to be a separate instance of VFP and that the environment was going to be the default settings.

Steve

>Steve,
>
>You probably don't have the environment setup right. Remember your DLL is going to fire up with all the default SET values. For example here's some code from a server I'm working on:
>
>
close database all
>set talk off
>set safety off
>set exclusive off
>set deleted on
>set century on
>set century to 19 rollover 95
>set multilocks on
>set console off
>set resource off
>
>on shutdown *
>
>local lcDrive
>
>if ( "DFSD" $ getenv( "machine" ) )
>   if ( "Pentium-II" $ getenv( "machine" ) )
>      lcDrive = "e:"
>   else
>      lcDrive = "h:"
>   endif
>else
>   lcDrive = "c:"
>endif
>
>set default to (lcDrive + "\vfp5app\project")
>Is the database already open in another VFP session?
>
>>I'm getting a "File Access denied" error message from within my DLL when trying to issue the VFP "OPEN DATABASE" command. I have successfully created the DLL with various class definitions in it and can instantiate objects using it. Are there certain VFP commands that a DLL will not process? My test program makes sure that the database is closed.
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform