Re: Other options beside seek
- From: "Guillem" <guillemvicens-nospam@xxxxxxxxxxxxxxxxxx>
- Date: 27 Apr 2006 02:18:05 -0700
Jeff Howard wrote:
I am using a server side cursor for an Access database and for
inserts into the database I am using a simple query returning the
primary key field(s) to determine if the record already exists or
not. This allows me to avoid using seek which forces me to re-index
based upon the primary key field(s) so that I do not have to change
the index back and forth and then from my query results I can either
do a AdoDataSet1.insert or edit. The nice thing about doing it this
way is that it also set the database pointer on the modified or
inserted record.
Sorry for the long introduction but I would like to know if there is
a quicker way then locate, since this does not care what index is
active, to go out and search or query as the user hits keystrokes
into an edit field and then to move the database pointer to an exact
match or at least the closest match? I know that the RecNo property
is really fast but I am not quite sure how get a record number
outside of seek or locate.
Thanks!
not really sure that is a good idea because it involves a lot of
movements. A workaround could be to use the Filter property, although I
am not sure that would be too fast either.
--
Best regards :)
Guillem Vicens Meier
Dep. Informatica Green Service S.A.
www.clubgreenoasis.com
--
Contribute to the Indy Docs project: http://docs.indyproject.org
--
In order to contact me remove the -nospam
.
- References:
- Other options beside seek
- From: Jeff Howard
- Other options beside seek
- Prev by Date: Re: Allowed values for ADOCommand.CommandText?
- Next by Date: Connect to MySQL 4.1 via ADO (ODBC)
- Previous by thread: Other options beside seek
- Next by thread: Connect to MySQL 4.1 via ADO (ODBC)
- Index(es):
Relevant Pages
|