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

Replicating backend during runtime

P: n/a
I am working with a production runtime Access 2000 db, split front-end
and back-end. Running on a network, I need a nightly copy of the
backend transferred to a laptop with a temporary network connection so
as to be able to run a locally linked version of the database outside
of the production environment. No data will be modified; it will be
read-only.

I am struggling with docmd.transferdatabase and trying to empty the
laptop-local version of the backend of relationships and tables, then
importing the current tables and relationships from the network copy
of the backend.

I looked into replication as well but I need to be able to make this
backend copy with users still working in the original backend. Is this
even possible? I am trying to avoid booting all users off to make this
copy as it needs to be made so one of the users can take it with them
when they leave (not neccesarily the last one to leave). Thoughts?
Suggestions?

- DAE
Nov 12 '05 #1
Share this Question
Share on Google+
5 Replies


P: n/a
First, you got to realize that the copy will not contain the current data at the
end of the day if the copy is made before the last person leaves.

It seems you are making this way harder than it needs to be. All you need do is
install the copy of the BE in a specific folder on the laptop. Each time you go
to install the next copy, it will overwrite the previous file so there's no need
to worry about doing anything with the existing file on the laptop. Then you
need a permanent copy of the front end linked to the tables in the backend in
whatever folder you always install the BE copy. The links will be different than
what is on the network but that's okay it will work fine as long as you point to
the folder where the BE is at. You can replace the BE with the next BE and the
FE will find all the links as long as nothing changes in the table structure of
the BE.
--
PC Datasheet
Your Resource For Help With Access, Excel And Word Applications
www.pcdatasheet.com
"Derickson" <ne****@vmmc.org> wrote in message
news:17**************************@posting.google.c om...
I am working with a production runtime Access 2000 db, split front-end
and back-end. Running on a network, I need a nightly copy of the
backend transferred to a laptop with a temporary network connection so
as to be able to run a locally linked version of the database outside
of the production environment. No data will be modified; it will be
read-only.

I am struggling with docmd.transferdatabase and trying to empty the
laptop-local version of the backend of relationships and tables, then
importing the current tables and relationships from the network copy
of the backend.

I looked into replication as well but I need to be able to make this
backend copy with users still working in the original backend. Is this
even possible? I am trying to avoid booting all users off to make this
copy as it needs to be made so one of the users can take it with them
when they leave (not neccesarily the last one to leave). Thoughts?
Suggestions?

- DAE

Nov 12 '05 #2

P: n/a
"PC Datasheet" <sp**@nospam.com> wrote in message news:<a9******************@newsread2.news.atl.eart hlink.net>...
First, you got to realize that the copy will not contain the current data at the
end of the day if the copy is made before the last person leaves.

It seems you are making this way harder than it needs to be. All you need do is
install the copy of the BE in a specific folder on the laptop. Each time you go
to install the next copy, it will overwrite the previous file so there's no need
to worry about doing anything with the existing file on the laptop. Then you
need a permanent copy of the front end linked to the tables in the backend in
whatever folder you always install the BE copy. The links will be different than
what is on the network but that's okay it will work fine as long as you point to
the folder where the BE is at. You can replace the BE with the next BE and the
FE will find all the links as long as nothing changes in the table structure of
the BE.
--
PC Datasheet
Your Resource For Help With Access, Excel And Word Applications
www.pcdatasheet.com


Yes, I understand that the copy made during runtime would not contain
the data entered post-replication but that cannot be helped. A copy
must be made before the user leaving so they can have the most current
data before departure. My problem is how to make a copy of the backend
while users are still logged into it. Simply browsing to the file on
the network, copying and pasting it to the local machine with a
locally linked front-end will not suffice. With users still logged in,
I do not want to chance corrupting the back-end.

I cannot boot all users off to make a copy so a simple file copy won't
work. Are there any other methods of replicating the backend while
reads and writes are being made?

- DAE
Nov 12 '05 #3

P: n/a
Any other suggestions?
Nov 12 '05 #4

P: n/a
I am afraid, not easily in the file server environment.
You could purge the laptop BE tables and append all the data from the
network BE. But you still won't get the locked records that users are
currently editing.
Maybe you could detect idle periods and then copy the data.

Pavel

Derickson wrote:

"PC Datasheet" <sp**@nospam.com> wrote in message news:<a9******************@newsread2.news.atl.eart hlink.net>...
First, you got to realize that the copy will not contain the current data at the
end of the day if the copy is made before the last person leaves.

It seems you are making this way harder than it needs to be. All you need do is
install the copy of the BE in a specific folder on the laptop. Each time you go
to install the next copy, it will overwrite the previous file so there's no need
to worry about doing anything with the existing file on the laptop. Then you
need a permanent copy of the front end linked to the tables in the backend in
whatever folder you always install the BE copy. The links will be different than
what is on the network but that's okay it will work fine as long as you point to
the folder where the BE is at. You can replace the BE with the next BE and the
FE will find all the links as long as nothing changes in the table structure of
the BE.

Nov 12 '05 #5

P: n/a
Hmm... then it is as I figured. Shoot. Well, maybe I can code
something to boot the users off after a warning message. Though if
they were editing a record, booting them off mid-update would corrupt
things too. I guess manually verifying that the ldb does not exist
after telling them to log off and then doing a direct file transfer is
the "best" solution. Thanks for the info/help.

- DAE

Pavel Romashkin <pa*************@hotmail.com> wrote in message news:<3F***************@hotmail.com>...
I am afraid, not easily in the file server environment.
You could purge the laptop BE tables and append all the data from the
network BE. But you still won't get the locked records that users are
currently editing.
Maybe you could detect idle periods and then copy the data.

Pavel

Nov 12 '05 #6

This discussion thread is closed

Replies have been disabled for this discussion.