Hi, GL.
> Is it risky too to make a backup, copy rename, across a network and in case
> of a problem to have a bad copy as well?Reference:: Sikh Philosophy Network http://www.sikhphilosophy.net/showthread.php?t=9377
The risk lies in an interrupted database write-to-disk operation, which is
more likely when conducted from across the network than when conducted from
the same workstation. Backups can be made using different methods, but when
conducting a backup via Microsoft Access, you are accessing the current
database file. You might notice that the file has increased in size after
you've created the backup file, which means that Jet was writing to the
original file during the backup. So it's a bit risky if you're trying to do
this across the network, and I wouldn't recommend it.
Copying and renaming a file from across the network is fine, as long as the
database is closed when you do so. The reason it should be closed is that if
someone is actively using it, then it could be in the middle of a write
operation when the file is copied, or it could be in the middle of a
transaction that has not yet been completed. The former would cause the file
to be marked as "suspect," as in possible file corruption. The latter would
cause loss of data integrity. (After all, you don't want a transaction that
debits your savings account to be halted before your checking account is
credited with the same amount, do you?) The reason that it's fine from
across the network is because while your workstation is passing the commands
to copy the file and paste it, the networked computer's operating system is
actually executing these two operations from its own queue, so there's a far
less likely chance of failure that these operations will be interrupted.
To safeguard the original file, make a copy of the database file before any
Reference:: Sikh Philosophy Network http://www.sikhphilosophy.net/showthread.php?t=9377
backup or compact of the database via Access, and then do the operation on
the copy, not the original.
HTH.
Gunny
See
http://www.QBuilt.com for all your database needs.
See
http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
http://www.Access.QBuilt.com/html/ex...ributors2.html for contact info.
"GL" wrote:
> Hi,
>
> I’ve read many times in this forum and elsewhere that is risky to compact a
> database from one computer to another across a network.
> Is it risky too to make a backup, copy rename, across a network and in case
> of a problem to have a bad copy as well?
>
> Thanks
> GL 
Our Donation Goal
: Why Donate? : Donate Today! : Donate Anonymously (ਗੁਪਤ) : Our Family of Supporters 
Linear Mode
