I wrote in the past some sub-routine (inDAO) in a Global Module something like:

Option Compare Database
Option Explicit
Public ws As Workspace
Public db As Database
Public tbInitialisatie As Recordset

Public Sub OpenInitialisatie()
On Error GoTo ErrorOpenInitialisatie
Set ws = DBEngine.Workspaces(0)
Set db = DBEngine.Workspaces(0).Databases(0)
Set tbInitialisatie = db.OpenRecordset("tblInitialisatie", DB_OPEN_TABLE)
MsgBox “DAO OK”
ExitError:
Exit Sub
ErrorOpenInitialisatie:
MsgBox "ErrorOpenInitialisatie DAO"
Resume ExitError
End Sub

Whan I split my tables, and I call this routine in a form, I get the message
"ErrorOpenInitialisatie DAO"

Yesterday I wrote the code (in ADO):

Option Compare Database
Option Explicit
Public tbInitialisatie As New ADODB.Recordset

Public Sub OpenInitialisatie()
tbInitialisatie.Open "tblInitialisatie", CurrentProject.Connection,
adOpenKeyset, adLockOptimistic
MsgBox “ADO OK”
ExitError:
Exit Sub
ErrorOpenInitialisatie:
MsgBox "ErrorOpenInitialisatie ADO"
Resume ExitError
End Sub

and I don't get the Erro-message anymore, but I get the 'good' message “ADO
OK”

I'm not so sure that I agree with that.

DAO might be the _OLD_ way to communicate with _JET_ files.
But 'Access Files' do not explicitly refer to MDB.  MDB is the
deprecrated format; it has not had any improvements since 1995.

DAO is too buggy for real world usage-- move to ADO.

-Aaron

On May 12, 2:13 pm, "Douglas J. Steele"
<NOSPAM_djsteele@NOSPAM_canada.com> wrote: