G
Guest
ENVIRONMENT: Windows XP Pro, Office/Access 2003 Pro.
Situation: to keep DB size reasonable and avoid "invalid argument" errors
generated when DB approaches 2gb, some tables are kept and periodically
updated in separate DBs, then linked to other DBs that make use of them.
Problem: "user" DBs need to use the SEEK method in VBA code. Indices
created in the "back end" DB of a linked file are not available for that
purpose, and code to create an index in the "user" DB fails if run against a
linked table.
Any suggestions? Only workaround I've come up with so far is to create a
cloned local copy of the table in the user database, which largely negates
any filesize benefit of having a linked table in the first place, even if I
delete the clone once it's no longer needed.
Situation: to keep DB size reasonable and avoid "invalid argument" errors
generated when DB approaches 2gb, some tables are kept and periodically
updated in separate DBs, then linked to other DBs that make use of them.
Problem: "user" DBs need to use the SEEK method in VBA code. Indices
created in the "back end" DB of a linked file are not available for that
purpose, and code to create an index in the "user" DB fails if run against a
linked table.
Any suggestions? Only workaround I've come up with so far is to create a
cloned local copy of the table in the user database, which largely negates
any filesize benefit of having a linked table in the first place, even if I
delete the clone once it's no longer needed.