Use the Connect property of the TableDef, and remember to RefeshLinks.
There is an example in solutions.mdb of how to check the lines on startup,
and - if the data is not found - pop up the Windows FileOpen dialog so the
user can locate it. Download from:
http://msdn.microsoft.com/library/de...dbdownload.asp
--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users -
http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.
"Sam DeRT" <sa*****@hotmail.com> wrote in message
news:f3**************************@posting.google.c om...
Is there a way to hard code what a path to a linked table would be
without
going through the Linked Table Manager or a re-linking process?
My issue is that I'm installing a database with linked tables onto
several
different networks. I can pre-determine what each path will be, but I
can't
do the re-linking or the Linked Table Manager remotely for each
network.
The files DbApp file and the DbData file both need to be installed on
each network because there will be multiple users in multiple
locations within a building.
Any work-arounds?