Sorry, I don't immediately know the answer to this one.
Are the source tables in another Access database or in some other form?
Can you not import directly from the source?

Bill Manville
MVP - Microsoft Excel, Oxford, England
No email replies please - respond to newsgroup

I suspect you may be suffering from MS Access getting confused with
Jet. Don't worry, it's a common problem, seemingly perpetuated by MS.

Jet is a database engine. MS Access provides GUI tools for managing
Jet databases plus a RAD environment for designing data-centric apps
based primarily, but not limited to, Jet databases. When you hear
'Access database' in this ng chances are they mean a Jet database
(this even seems to be true of the MS Access ngs).

A .mdb file is a Jet database. Tables in the Jet database hold the
database's data, schema, constraints, stored procedures/queries, etc.
For a MS Access application, Jet also holds the forms, reports etc. MS
seem to enjoy blurring the picture of Jet and MS Access e.g.
'Microsoft Access Driver', why not Jet driver?

You do not need MS Access to create, maintain or query a Jet database,
including creating linked tables; you merely need Jet and MDAC, both
of which are available to most Excel users. I'm currently working on a
tool which creates/refreshes linked tables in a Jet database created
on the fly, using 'Microsoft ActiveX Data Objects Extensions for Data
Definition Language and Security' (ADOX for short); I don't use MS
Access.

When you create a linked table using ADOX, there are some useful
properties you can explicitly set e.g. you can specify the connection
string to the provider you are linking to, specify whether to cache
the password, etc.

(This is where my knowledge goes a bit fuzzy because I'm not an MS
Access user.) When you do the same in MS Access, these things are done
implicitly so I don't know if MS Access does things the same way. From
what I read it seems MS Access holds the info, but I can't be sure and
I don't know where it would store e.g. the password (not in the system
tables nor the registry AFAIK).

Here's my suggestion, which you may not like: re-create your links
without using MS Access. This way you will be in control of the
details. You will find these MSDN articles invaluable:

ADO Provider Properties and Settings
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnacc2k/html/ad
oproperties.asp

Creating a Linked Table
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odeopg/html/deo
vrcreatinglinkedtable.asp

Creating an Access Database [<< see what I mean?!]
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odeopg/html/deo
vrcreatingaccessdatabase.asp

FWIW as a test I just now used ADOX to create a linked table in a Jet
database to a table in a password-protected Jet database, then
successfully accessed the linked table using ODBC in MS Query.

Alternatively, you could post your question in one of the MS Access
ngs. However, I suspect you'll run into the opposite problem e.g.
someone who knows a lot about MS Access but whose knowledge starts to
get fuzzy when the talk turns to how Jet does things when MS Access is
not involved. Also bear in mind that MS Access's raison d'etre as a
GUI front-end for Jet is to hide complexity from the user...

--