VBA Error 3251

  • Thread starter Thread starter Magster
  • Start date Start date
M

Magster

Hi

I'm trying to use the seek command using an alternate index on a table
located in a linked back-end database in Access 2007.

My routine works great when I move the table into the front-end database,
but when I want to use the production in the linked back-end, it gives me the
3251 - "Current provider does not support the necessary interface for Index
functionality"

So, I have two questions:
1. Can I use an alternate index on a table that is located in a linked
backend database using the seek command in either ADO or DAO?

2. In the "About Microsoft Access..." I noticed that Jet 4.0 and ODBC do
not have a path available in my database. Could this be why I couldn't get
the info from an article ID #249683 (support.microsoft.com) to work with
it's suggested workaround which indicated a direct connection and a provider
of Jet.OLEDB.4.0?

My sincere thanks in advance!
 
Magster said:
Hi

I'm trying to use the seek command using an alternate index on a table
located in a linked back-end database in Access 2007.

My routine works great when I move the table into the front-end database,
but when I want to use the production in the linked back-end, it gives me
the
3251 - "Current provider does not support the necessary interface for
Index
functionality"

So, I have two questions:
1. Can I use an alternate index on a table that is located in a linked
backend database using the seek command in either ADO or DAO?

2. In the "About Microsoft Access..." I noticed that Jet 4.0 and ODBC do
not have a path available in my database. Could this be why I couldn't
get
the info from an article ID #249683 (support.microsoft.com) to work with
it's suggested workaround which indicated a direct connection and a
provider
of Jet.OLEDB.4.0?

My sincere thanks in advance!
Click to expand...

1. No. The seek command requires local data.

2. What do you mean by "do not have a path available in my database"
If you're wondering where the path information is stored for a linked table,
the answer is the TableDef's Connect property:

Debug.Print CurrentDb.TableDefs("MyLinkedTable").Connect
 
Back
Top