Re: Trouble with DAO "SEEK" in converting application to SQL Express back end.
- From: "David W. Fenton" <XXXusenet@xxxxxxxxxxxxxxxxxxx>
- Date: Thu, 30 Mar 2006 16:59:19 -0600
"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 news:bDUWf.202692$H%4.69991@pd7tw2no:
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.
Is SEEK a Jet-only operation? Given that it's based on indexes, I'd
think that it would be.
I don't think there are very many situations at all where SEEK is
justified at all. Either filter your recordset or use .FindFirst.
The latter may very well be 10 times slower than SEEK, but that
would only matter if you're doing loops that require hundreds of
thousands of operations that reposition the current record pointer.
--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/
.
- Prev by Date: Use SendObject Property to email designated person who is listed in a table
- Next by Date: Re: SP2 seriously Impacts Access 97 Performance
- Previous by thread: Use SendObject Property to email designated person who is listed in a table
- Next by thread: Re: Trouble with DAO "SEEK" in converting application to SQL Express back end.
- Index(es):
Relevant Pages
|
