> The references get released on WinNT machine but I am using Win2000
I have never used the Visual FoxPro Driver. But two things I can think of
that are worth doing:
1. Dump the Connection's Properties before/after a successful Open. You want
to dump the name and value. The number of Properties expands after a
successful Open(). It could be that Visual FoxPro Driver has a dynamic
property called, say, "ReleaseConnectionTimeout" that is of value 60. Who
This link may help
2. ADO supports this concept of Connection Pooling. This could interfere. It
could be it is switched on for your Win2000 machine and switched off on your
WinNT machine. Have a look here
and read under "OLE DB Pooling". This statement in the doucmentation seems
"The time-out value is set to 60 seconds; this value cannot be configured in
OLE DB resource pooling prior to the release of MDAC 2.5."
I am no expert, but I would poke with a sharp stick in the Registry, examine
what is offered by Connection object under Visual FoxPro and read all
Microsoft articles and compare with documentation. If "Connection pooling"
turns out to be right, my guess would be you want to manually override
whatever the state of Connection pooling is on a particular Windows machine
for consistency. Looks to me like you want "OLE DB Services=n;" in the
Connection string somewhere before you open. If you dump the Connection
properties on both Windows machines after a successful Open(), it should
show what this property is set to.
Hope this helps