M
MyndPhlyp
Arghh.
(Fear not. That rhythmic thumping you hear is only the sound of my head
repeatedly hitting the desk.)
Working with a series of Access, Btrieve (linked) and FoxPro (linked)
tables, I'm opening some known closed ADODB.Recordsets after a lengthy
(1-1/2 hrs) number crunching and read/write session. That number crunching
session includes several tables from each source. When I push on to the next
phase, the Btrieve tables open just fine, but the FoxPro tables crash and
burn on the first .Open attempt. (Nothing was closed, including the
Connection, at the end of the long running phase.)
If I close out the application, fire it up again and pick up where I left
off with the step that crashed, the tables open right up and life is
wonderful.
The ADODB.Connection I am using is nothing more than
CurrentProject.Connection. I'm at MDAC v2.8 and Jet v4.0/SP8.
The FoxPro tables are being accessed via an ODBC DSN using Microsoft Visual
FoxPro Driver v6.01.8630.01.
The Btrieve tables are likewise being accessed via an ODBC DSN, but using
the Pervasive driver v8.10.117.17.
The Access tables are all local - no linking.
Anybody know of any timeout or other settings that might be causing an
rs.Open on a linked FoxPro table to crash after some lengthy processing?
(Fear not. That rhythmic thumping you hear is only the sound of my head
repeatedly hitting the desk.)
Working with a series of Access, Btrieve (linked) and FoxPro (linked)
tables, I'm opening some known closed ADODB.Recordsets after a lengthy
(1-1/2 hrs) number crunching and read/write session. That number crunching
session includes several tables from each source. When I push on to the next
phase, the Btrieve tables open just fine, but the FoxPro tables crash and
burn on the first .Open attempt. (Nothing was closed, including the
Connection, at the end of the long running phase.)
If I close out the application, fire it up again and pick up where I left
off with the step that crashed, the tables open right up and life is
wonderful.
The ADODB.Connection I am using is nothing more than
CurrentProject.Connection. I'm at MDAC v2.8 and Jet v4.0/SP8.
The FoxPro tables are being accessed via an ODBC DSN using Microsoft Visual
FoxPro Driver v6.01.8630.01.
The Btrieve tables are likewise being accessed via an ODBC DSN, but using
the Pervasive driver v8.10.117.17.
The Access tables are all local - no linking.
Anybody know of any timeout or other settings that might be causing an
rs.Open on a linked FoxPro table to crash after some lengthy processing?