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

Create a back-end copy while it is still in use.

P: n/a
I have a situation where I need to create a copy of the back-end for a person
who goes on the road (Remote Back-End). It needs to be as current as
possible, so this will generally mean that others are accessing the main back-
end at the time we need to create the copy.

In reading through some posts, VB FileCopy won't work (which I've tested). I
also tested fso.CopyFile (file scripting) and that seems to always be able to
create a copy even if the main back-end file is in use. But it seems
dangerous to use this.

Other suggestions. I think someone suggested deleting all tables in the
remote back-end and then exporting the tables from the main backend to the
remote backend. If this is a good way to do this, is there code available
for doing this. I'm an intermediate programmer, but I'm weak on dealing with
Make table queries, etc.

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...ccess/200608/1

Aug 9 '06 #1
Share this Question
Share on Google+
6 Replies


P: n/a
rdemyan via AccessMonster.com wrote:
I have a situation where I need to create a copy of the back-end for a person
who goes on the road (Remote Back-End). It needs to be as current as
possible, so this will generally mean that others are accessing the main back-
end at the time we need to create the copy.

In reading through some posts, VB FileCopy won't work (which I've tested). I
also tested fso.CopyFile (file scripting) and that seems to always be able to
create a copy even if the main back-end file is in use. But it seems
dangerous to use this.

Other suggestions. I think someone suggested deleting all tables in the
remote back-end and then exporting the tables from the main backend to the
remote backend. If this is a good way to do this, is there code available
for doing this. I'm an intermediate programmer, but I'm weak on dealing with
Make table queries, etc.
Go to explorer
Select the file.
Ctrl+C/Ctlr+V

I've never had a problem with this method. Maybe others have. I'll go
with what works until it doesn't.
Aug 9 '06 #2

P: n/a
Yes, but someone may be accessing data or worse writing data to the back-end
file during the copying process in Explorer.

salad wrote:
>I have a situation where I need to create a copy of the back-end for a person
who goes on the road (Remote Back-End). It needs to be as current as
[quoted text clipped - 11 lines]
>for doing this. I'm an intermediate programmer, but I'm weak on dealing with
Make table queries, etc.

Go to explorer
Select the file.
Ctrl+C/Ctlr+V

I've never had a problem with this method. Maybe others have. I'll go
with what works until it doesn't.
--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...ccess/200608/1

Aug 9 '06 #3

P: n/a
rdemyan via AccessMonster.com wrote:
Yes, but someone may be accessing data or worse writing data to the back-end
file during the copying process in Explorer.
True. You mentioned "It needs to be as current". The way I view
backups is that a backup is a snapshot of the way things were at the
exact second the copy was made. If you want a perfect backup, get
everyone out, make a copy, let them back in. Within minutes the backup
is out of date as people start adding/modifying records.

Actually, a good method for your traveling user is GoToMyPC if he can
connect to the internet. If he's on broadband it's almost like he's at
the home office.

Aug 9 '06 #4

P: n/a
Actually, by worse I was referring to potential corruption. I'd like the
data to be as current as practical, but my real concern is avoiding
corruption.

Thanks.

salad wrote:
>Yes, but someone may be accessing data or worse writing data to the back-end
file during the copying process in Explorer.

True. You mentioned "It needs to be as current". The way I view
backups is that a backup is a snapshot of the way things were at the
exact second the copy was made. If you want a perfect backup, get
everyone out, make a copy, let them back in. Within minutes the backup
is out of date as people start adding/modifying records.

Actually, a good method for your traveling user is GoToMyPC if he can
connect to the internet. If he's on broadband it's almost like he's at
the home office.
--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...ccess/200608/1

Aug 9 '06 #5

P: n/a
rdemyan via AccessMonster.com wrote:
Actually, by worse I was referring to potential corruption. I'd like the
data to be as current as practical, but my real concern is avoiding
corruption.
Like I said b4, I've never had a problem with it. If I did, I'd stop
that method, kick everyone out, and then create one. Usually I do my
method so I can do testing on the database.

Aug 10 '06 #6

P: n/a
Bri

salad wrote:
rdemyan via AccessMonster.com wrote:
>Actually, by worse I was referring to potential corruption. I'd like
the
data to be as current as practical, but my real concern is avoiding
corruption.


Like I said b4, I've never had a problem with it. If I did, I'd stop
that method, kick everyone out, and then create one. Usually I do my
method so I can do testing on the database.
I would think that if you make the copy while data is being written to a
table (particularly one with indexes) that the chance of the COPY being
corrupt are definately possible. The data could be out of sync with the
index, a Parent Table could be out of sync with its child records, etc.
I doubt that the original DB would ever be corrupted by this, but others
may know more.

--
Bri

Aug 14 '06 #7

This discussion thread is closed

Replies have been disabled for this discussion.