Link Tables

[Alex Martinez]

Hello,

I have a problem that I am trying to resolve and I need some professional
tips. I am developing a front end database (queries, forms, reports)
residing in a branch in Texas in their server drive F: I am located in
California I have mapped a drive (E) to be able to update or enhance the
database from their server. Now the back end database (tables) resides in
California server. The problem is if I go in the front end database in the
Texas server and link the tables (back end) through our server in drive F:
it works fine not a problem, but when the Texas user tries to open the table
they get an error message stating something like this: "invalid path". I
had the user in Texas created a new drive (J) to map into our server in
California and they were able to link the tables without a problem, but now
I get the "invalid path" error message if I try to access the front end
database. I am at a lost on this one. I even created a (J) drive to mapped
in our California server thinking maybe that both (J) drive in Texas and in
California will work, but it didn't. How can I have the branch in Texas or
in California link a new table without getting this invalid path error
message? It seems it's one or the other, but not both. What I want is the
user have the ability to link a new table in Texas without get this error
message or if I make a new table in California and try to link it we won't
get this error message. From time to time I visit the Texas branch and I
really need to have capability to add a table when needed. Any tips or
suggestion on visiting a website will be appreciated. Thank you.

 

[Amy Blankenship]

You'll either need to make sure the structure is identical or create startup
code that checks for the valid path and reconnects everything in the
background. This code could be designed to write unc paths which should
prevent future problems.

HTH;

Amy

 

[jacksonmacd]

If you are attempting to open an Access database over a WAN, you
should read this article before proceeding:

http://www.members.shaw.ca/AlbertKallal/Wan/Wans.html

Hello,

I have a problem that I am trying to resolve and I need some professional
tips. I am developing a front end database (queries, forms, reports)
residing in a branch in Texas in their server drive F: I am located in
California I have mapped a drive (E) to be able to update or enhance the
database from their server. Now the back end database (tables) resides in
California server. The problem is if I go in the front end database in the
Texas server and link the tables (back end) through our server in drive F:
it works fine not a problem, but when the Texas user tries to open the table
they get an error message stating something like this: "invalid path". I
had the user in Texas created a new drive (J) to map into our server in
California and they were able to link the tables without a problem, but now
I get the "invalid path" error message if I try to access the front end
database. I am at a lost on this one. I even created a (J) drive to mapped
in our California server thinking maybe that both (J) drive in Texas and in
California will work, but it didn't. How can I have the branch in Texas or
in California link a new table without getting this invalid path error
message? It seems it's one or the other, but not both. What I want is the
user have the ability to link a new table in Texas without get this error
message or if I make a new table in California and try to link it we won't
get this error message. From time to time I visit the Texas branch and I
really need to have capability to add a table when needed. Any tips or
suggestion on visiting a website will be appreciated. Thank you.

**********************
(e-mail address removed)
remove uppercase letters for true email
http://www.geocities.com/jacksonmacd/ for info on MS Access security