Re: Trouble with DAO "SEEK" in converting application to SQL Express back end.
- From: "Larry Linson" <bouncer@xxxxxxxxxxxxx>
- Date: Fri, 31 Mar 2006 00:10:29 GMT
"Rico" wrote
When I remove the dbOpenTable, it works but
I can't use the SEEK method on the index.
You have never been able to use dbOpenTable or Seek on anything but native
Jet tables in the same MDB/MDE. As far as I know, that is well-documented.
My personal view is that use of SEEK most often implies a poor design --
there may be a few cases in which it is needful to open a dataset with a
large number of records, and then find the one you want (SEEK if you can
open as a Table, or FIND / FINDFIRST if opened as a Dynaset).
It is more efficient, especially if you are using an Access client with a
Server DB (as you are now), to include criteria in your Query or SQL
statement so that the extraction of the one record you want is performed at
the server (or no record if it does not exist). It is really amazing to
realize just how often we need only one record (if it exists) or none (if it
does not exist).
Larry Linson
Microsoft Access MVP
.
- Follow-Ups:
- Re: Trouble with DAO "SEEK" in converting application to SQL Express back end.
- From: David W. Fenton
- Re: Trouble with DAO "SEEK" in converting application to SQL Express back end.
- Prev by Date: Re: Ethical Database Practice?
- Next by Date: Re: if table exist
- Previous by thread: Re: Trouble with DAO "SEEK" in converting application to SQL Express back end.
- Next by thread: Re: Trouble with DAO "SEEK" in converting application to SQL Express back end.
- Index(es):
Relevant Pages
|
