Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Possible Bug in COM DLL's
Message
General information
Forum:
Visual FoxPro
Category:
Other
Title:
Possible Bug in COM DLL's
Miscellaneous
Thread ID:
00561683
Message ID:
00561683
Views:
47
I have found what I think is a possible bug in multi-threaded COM components.

My component is running under COM+ on Win2k sp1. The DLL makes some calls to
SQL Server 7.0 stored procedures and returns the results to the client either
as a discrete value or as an XML string.

My test client makes 4 calls to the component. In the first 2 calls, the HOME()
directory is reported as the directory where the .DLL is physically located.
The next 2 calls report HOME() as C:\Program Files\Common Files\Microsoft Shared\VFP\
(IOW, the directory where the runtime is located.) SYS(2004) does the same thing but
CURDIR() always reports \WINNT\SYSTEM32\ and SYS(16,1) always returns the proper
setting.

If HOME() returns the directory where VFP was started why would it sometimes
return the directory where the COM .DLL is located?
Next
Reply
Map
View

Click here to load this message in the networking platform