Leemi
Wed Oct 12 16:05:19 CDT 2005
Hi Chip:
I have not heard of this behavior. However, if this is the same project
file that has been migrated from VFP 6.0, I would create a new project
file, add the code for the DLL to it, and compile a new MT DLL in VFP 9.0
and try it. The project file might have some correction that gets built
into the DLL and causes this behavior.
I hope this helps.
This posting is provided "AS IS" with no warranties, and confers no rights.
Sincerely,
Microsoft FoxPro Technical Support
Lee Mitchell
*-- VFP9 HAS ARRIVED!! --*
Read about all the new features of VFP9 here:
http://msdn.microsoft.com/vfoxpro/
*--Purchase VFP 9.0 here:
http://www.microsoft.com/PRODUCTS/info/product.aspx?view=22&pcid=54787e64-52
69-4500-8bf2-3f06689f4ab3&type=ovr
Keep an eye on the product lifecycle for Visual FoxPro here:
http://support.microsoft.com/gp/lifeselectindex
- VFP5 Mainstream Support retired June 30th, 2003
- VFP6 Mainstream Support retired Sept. 30th, 2003
>I have a COM server I've written, starting in VFP 6, using the combination
>of Session and OLEPublic classes. This is used by other apps such as
>WordPerfect and Word to retrieve some data from our foxpro tables, and has
>worked well for years in VFP 6, 7, and 8.
>Now, when I try and compile it in 9, it is taking approximately 30 seconds
>to close the running instance of it, when it's used, and this leaves a
white
>square on the display of the calling app, and renders it unusable during
>this time. Until now it's closed almost instantly.
>Does anyone have any guesses as to what's going on and what's different
>about VFP 9? This is run under win2k and Win XP.
>Thanks.
>Chip