Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Declare DLL call caused an exception
Message
From
29/06/2000 15:27:05
 
 
To
29/06/2000 11:39:19
General information
Forum:
Visual FoxPro
Category:
Troubleshooting
Miscellaneous
Thread ID:
00386312
Message ID:
00386677
Views:
18
>>>I have this message:
>>>
>>>Declare DLL call caused an exception
>>>
>>>What info can I additionaly get about this message?
>>
>>Hard to say, Michel, without the declaration.
>
>It's hard to say also from the line it has been reported. The line is something like this:
>
>IF NOT GetResult()
>
>GetResult() is a function a mine. However, that functions deals with some calls to a DLL. So, I am wondering why the error is being reported at that line and not in the line of the function.

It indicates that the error is actually occuring on exiting from the function GetResult() in all probability; it may be an effect resulting from the release of local or private memvars declared in the GetResult function code; especially likely if a memvar is used as a return buffer from some API calls that expect you to explicitly dispose of a buffer (eg some of the calls that use the NetApiBuffer stuff in the Net* family of calls.)
EMail: EdR@edrauh.com
"See, the sun is going down..."
"No, the horizon is moving up!"
- Firesign Theater


NT and Win2K FAQ .. cWashington WSH/ADSI/WMI site
MS WSH site ........... WSH FAQ Site
Wrox Press .............. Win32 Scripting Journal
eSolutions Services, LLC

The Surgeon General has determined that prolonged exposure to the Windows Script Host may be addictive to laboratory mice and codemonkeys
Previous
Reply
Map
View

Click here to load this message in the networking platform