A2003 link to Foxpro OBDC Error 3626 Too many indexes

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Access 2003 SP1 XP SP2 OBDC Machine linking to some Visual Fox Pro tables
returns "The operation failed. There are too many indexes on table <name>.
Delete some of the indexes on the table and try the operation again. (Error
3626).

Is there any way around without exporting a stripped down version of this
table from Fox Pro??
 
Hi Tede,

Do you have a way of knowing how many indexes there are or what the index
expressions are?
 
Sorry, server was off line , I do not know how many indexes, and am not sure
what the index expression is, (what you mean). I hope to get that information
from the vendor FCSI ASAP depending on the holiday schedule. Thank you. I
can export to a snapshot and import but I would like to link directly if
possible.
 
Hi Tede,

An index expression would be something like:

Index On PadR(Upper(Alltrim(LastName) + ", " + FirstName), 30) Tag WholeName
 
Thank You, I am a step further.
I think I hit the too many options overload, the "VFP" files end in dbf and
the index files are .cdx ?? not what I expected for VFP, so I removed the
..cdx index files and used the ODBC link ( no option for .cdx in index list).
I now link to the table but only get 12K rows, not the entire file. I think
you are suggesting a VB or SQL solution? would this eliminate the 12k row
limit? I'm sure you tire of the confused novices, since FoxPro and Access are
often changing I would be happy to attempt or research any method that will
work.
 
Back
Top