Re: Trouble with DAO "SEEK" in converting application to SQL Express back end.

SEEK is a fast native Access/Jet method.

If you want the same performance from SQL Server 2005,
you are going to need to use SQL Server native methods.

However, there are alternatives. At this point, you have
the choice of using ADO methods, DAO methods, or Stored
Procedures.

I can't say that there is much to choose between them.
Make a personal decision, flip a coin, or ask a friend.

Then ask here for an example using your chosen technology.
You will have to give an example of what you are trying
to do, because there is no direct plug-in replacement.

(david)


"Rico" <r c o l l e n s @ h e m m i n g w a y . c o mREMOVE THIS PART IN
CAPS> wrote in message news:bDUWf.202692$H%4.69991@xxxxxxxxxxx
Hello,

I have an application that I'm converting to Access 2003 and SQL Server
2005 Express. The application uses extensive use of DAO and the SEEK
method on indexes. I'm having an issue when the recordset opens a table.
When I write

Set rst = db.OpenRecordset("MyTable",dbOpenTable, dbReadOnly)

I get an error. I believe it's invalid operation or invalid parameter,
I'm not in front of the application at the moment, but will let you know
if it's important.

When I remove the dbOpenTable, it works but I can't use the SEEK method on
the index.

Any ideas?

Thanks!




.