Seek method after split database

[dhstein]

I know there's a way to use the seek method after splitting the database.
I've seen advice like this:

"Keep in mind that Seek only works on table-type recordsets. Once you
split the database in front-end and back-end, you need to have a
global database object that refers to the back-end. Then you can
continue to use Seek. "

But I'm having trouble setting up the connection string and the ODBC
references. I've seen numerous examples but none of them are working for me.
Can anyone suggest a reference book that might make this clear. Thanks for
any help.

 

[Larry Linson]

You open the "back end" (tables, data, and relationships) database directly,
then open the table as a table-type recordset (the only kind with which you
can use "seek"). However, I generally find it both easier, and faster in
performance, to open a dynaset, or a snapshot, using SQL that selects the
record instead of opening the entire table and seeking a particular record.

Larry Linson
Microsoft Office Access MVP

 

[Albert D. Kallal]

I know there's a way to use the seek method after splitting the database.
I've seen advice like this:

"Keep in mind that Seek only works on table-type recordsets. Once you
split the database in front-end and back-end, you need to have a
global database object that refers to the back-end. Then you can
continue to use Seek. "

But I'm having trouble setting up the connection string and the ODBC
references. I've seen numerous examples but none of them are working for
me.
Can anyone suggest a reference book that might make this clear. Thanks
for
any help.

You don't have to setup a odbc ref, you just have to open up the back end
directly....

there is a "general" function to return a reocrdset that allows seek when
you database is split here:

http://www.mvps.org/access/tables/tbl0006.htm

 

[a a r o n . k e m p f]

wow dude, it sounds like your engineless database is just a huge pain
in the ass

sounds to me like it would just be a lot easier if you just used SQL
Server.

maybe you should just use a database system that comes with TOOLS for
indexing
then you wouldn't have to get so worked up about access bugs

-Aaron

 

[David W. Fenton]

I know there's a way to use the seek method after splitting the
database.

Don't.

Really.

It is not really useful except in extremely rare circumstances.

Abandon it now, instead of investing all the time it takes in
re-engineering your app to continue to use a non-portable data
access method. It's just a bad idea and the performance gain with
SEEK over other methods is just not relevant with modern computers,
except in very unusual applications that would need to jump around a
recordset to many records in rapid succession. The real-world cases
for that are vanishingly small.

Bite the bullet and get away from SEEK permanently now.