S
ScottB
[This message was posted today in the 'Forms Programming'
section but no real solution provided ...perhaps here?]
I created a test database with one small table and one
form. The form has one button on it that activates the
following event (copied in part):
Private Sub Command0_Click()
Dim curdb As DAO.Database
Dim rst As DAO.Recordset
Dim nm as String
Set curdb = CurrentDB
Set rst = curdb.OpenRecordset ("Table1", dbOpenTable)
With rst
....
The form, in fact, works fine "until" I used the Database
Splitter to separate it into front and back ends. Then,
when I try to use the same form it gives me a "Run-time
error '3219'; Invalid Operation" and crashes on the line
reading
Set rst = curdb.OpenRecordset ("Table1", dbOpenTable)
The program this simple test database was patterned after
worked fine about 6 mo. ago (even when split). My hunch
is that it has to do with an upgrade to Windows Server
2003 and less support for DAO libraries in Access 2002;
I'm using Microsoft DAO 3.6 Object Library for this test
database. Because of extensive naming conventions and
multiple databases used in my main project, I can't simply
bring tables all back into one project. From what I've
read about ADO, I think I'm better off staying with DAO
since it's all-Access and few users. Any sage words of
advice would really, really be appreciated. Scott
section but no real solution provided ...perhaps here?]
I created a test database with one small table and one
form. The form has one button on it that activates the
following event (copied in part):
Private Sub Command0_Click()
Dim curdb As DAO.Database
Dim rst As DAO.Recordset
Dim nm as String
Set curdb = CurrentDB
Set rst = curdb.OpenRecordset ("Table1", dbOpenTable)
With rst
....
The form, in fact, works fine "until" I used the Database
Splitter to separate it into front and back ends. Then,
when I try to use the same form it gives me a "Run-time
error '3219'; Invalid Operation" and crashes on the line
reading
Set rst = curdb.OpenRecordset ("Table1", dbOpenTable)
The program this simple test database was patterned after
worked fine about 6 mo. ago (even when split). My hunch
is that it has to do with an upgrade to Windows Server
2003 and less support for DAO libraries in Access 2002;
I'm using Microsoft DAO 3.6 Object Library for this test
database. Because of extensive naming conventions and
multiple databases used in my main project, I can't simply
bring tables all back into one project. From what I've
read about ADO, I think I'm better off staying with DAO
since it's all-Access and few users. Any sage words of
advice would really, really be appreciated. Scott