Wrong default workspace?

  • Thread starter Thread starter Richard
  • Start date Start date
R

Richard

We just upgraded from Access 97 to Access 2002. Our in-
house databse application transfered over with few
problems. One of the most vexing is that our seek commands
stopped working. Apparently, they are not available in an
ODBC workspace.

We've always used a Jet workspace. Why are we suddenly in
an ODBC workspace? How do we tell Access to use a Jet
workspace instead?

The help says to use a CreateWorkspace command. Including
the command in the routine that is trying to use Seek
doesn't help. Where should we put the command?
 
"ODBC Workspace"? Did you change to using a server database as your back
end?

Seek commands only work on Table-type recordsets, not on Dynasets which
result from Queries, and are the only option for Linked Tables.

In fact, you cannot access a Jet database from Access via ODBC. That's the
primary reason I am wondering what you mean by "ODBC workspace" and what you
may not have told us.

Larry Linson
Microsoft Access MVP
 
The first thing to verify since you went form Access 97 to Access 2002 is that you have a
reference set to DAO. Also, change all of your Dim statements that reference DAO items to
specifically specify DAO.

To set the reference, open a code module (Alt+F11) and go to Tools|References. If DAO is
checked, verify the version. If it is old, uncheck it and check the newer one. If one
isn't checked, check the newest one. The one you want is Microsoft DAO 3.6 Object Library.

To change your Dim statements you should be able to use Replace (Ctrl+H) and tell it to
make the changes through the whole project.

Example:
What to change: As Database
Change to: As DAO.Database

Also do this for other DAO objects such as Recordset, QueryDef, Workspace, etc.
 
Back
Top