By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
459,290 Members | 1,427 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 459,290 IT Pros & Developers. It's quick & easy.

Networking Access

P: n/a
I have the backend database on a network drive. There are 3 employees that
access this backend database through their respective frontend databases
(located on their respective C drive).
One of these employees has a laptop.
Q1. The laptop provides a problem in that each time it is connected to the
network, he cannot access the backend. The database window still has the
linked tables. The only remedy is to simply deleted the linked tables in the
frontend and then proceed to create the link tables in the frontend (again).
This is frustrating. Any suggestions how this can be overcome without any
user intervention.... allowing him/her to simple start using the database
when hooked up to the network.

Q2. There will be updates in the future to the database, which means that I
would have to ammend each individual pc that contains the frontend database.
And as the company grows, pc numbers (frontend) will increase. If I have one
frontend on the network, would their be sharing violations? or a probability
that there would be corruption to data when everyone was using this one
frontend the network ?
thanks for any help.
Jul 9 '06 #1
Share this Question
Share on Google+
2 Replies


P: n/a

"Gary" <sk**@optusnet.com.auwrote in message
news:44***********************@news.optusnet.com.a u...
>I have the backend database on a network drive. There are 3 employees that
access this backend database through their respective frontend databases
(located on their respective C drive).
One of these employees has a laptop.
Q1. The laptop provides a problem in that each time it is connected to the
network, he cannot access the backend. The database window still has the
linked tables. The only remedy is to simply deleted the linked tables in
the frontend and then proceed to create the link tables in the frontend
(again). This is frustrating. Any suggestions how this can be overcome
without any user intervention.... allowing him/her to simple start using
the database when hooked up to the network.
There is an article which demonstrates how to re-link Access tables from
code here: http://www.mvps.org/access/tables/tbl0009.htm

Q2. There will be updates in the future to the database, which means that
I would have to ammend each individual pc that contains the frontend
database. And as the company grows, pc numbers (frontend) will increase.
If I have one frontend on the network, would their be sharing violations?
or a probability that there would be corruption to data when everyone was
using this one frontend the network ?
thanks for any help.

Tony has created an excellent app for keeping your frontend's up to date.
http://www.granite.ab.ca/access/autofe.htm
Jul 9 '06 #2

P: n/a
About Q2. just a suggestion - you can think about having a webpage on
your network that accesses the back end, that way you only need to
change the webpage. This way you can control violations using code.
Contact me for more information if necessary.

Sorry dont know what the problem is with the laptop - sounds like a
network problem to me - but not sure.

Colin Possamai

Gary wrote:
I have the backend database on a network drive. There are 3 employees that
access this backend database through their respective frontend databases
(located on their respective C drive).
One of these employees has a laptop.
Q1. The laptop provides a problem in that each time it is connected to the
network, he cannot access the backend. The database window still has the
linked tables. The only remedy is to simply deleted the linked tables in the
frontend and then proceed to create the link tables in the frontend (again).
This is frustrating. Any suggestions how this can be overcome without any
user intervention.... allowing him/her to simple start using the database
when hooked up to the network.

Q2. There will be updates in the future to the database, which means that I
would have to ammend each individual pc that contains the frontend database.
And as the company grows, pc numbers (frontend) will increase. If I have one
frontend on the network, would their be sharing violations? or a probability
that there would be corruption to data when everyone was using this one
frontend the network ?
thanks for any help.

Jul 10 '06 #3

This discussion thread is closed

Replies have been disabled for this discussion.