Mirroring Database

[GGerard]

Hello

Does anyone know if there's a way to mirror data from a backend database to
a second database?

Example: When writing data to one database it would mirror the data in a
second database for backup
and then if anything should happen to the first database the user could
switch to the second backup database.

I can see it done be writing a lot of code but is there a way that it could
be done automatically.

Thanks
G.Gerard

[Larry Linson]

There is no builtin feature for this.

You could write code. It might be better to invest in a server database that
has high availablilty, reliability, and recoverability features. In most
cases, you can still use much of your Access database application as the
client to the server database.

Larry Linson
Microsoft Access MVP

"GGerard" <gg*****@nbnet.nb.ca> wrote in message
news:SX**********************@ursa-nb00s0.nbnet.nb.ca...

Hello

Does anyone know if there's a way to mirror data from a backend database to a second database?

Example: When writing data to one database it would mirror the data in a
second database for backup
and then if anything should happen to the first database the user could
switch to the second backup database.

I can see it done be writing a lot of code but is there a way that it could be done automatically.

Thanks
G.Gerard

[PC Datasheet]

Use a split database with two backends. If something happens to the first
backend, have a button in the front end with code to change the connection
string of all the tables to the second database.

--
PC Datasheet
Your Resource For Help With Access, Excel And Word Applications
re******@pcdatasheet.com
www.pcdatasheet.com
"GGerard" <gg*****@nbnet.nb.ca> wrote in message
news:SX**********************@ursa-nb00s0.nbnet.nb.ca...

Hello

Does anyone know if there's a way to mirror data from a backend database to a second database?

Example: When writing data to one database it would mirror the data in a
second database for backup
and then if anything should happen to the first database the user could
switch to the second backup database.

I can see it done be writing a lot of code but is there a way that it could be done automatically.

Thanks
G.Gerard

[Trevor Best]

GGerard wrote:

Hello

Does anyone know if there's a way to mirror data from a backend database to
a second database?

Example: When writing data to one database it would mirror the data in a
second database for backup
and then if anything should happen to the first database the user could
switch to the second backup database.

I can see it done be writing a lot of code but is there a way that it could
be done automatically.

For hardware failures, simply use mirrored disks on the server or more
esoteric RAID 0+1, 5, 10, 50, etc.

There are other options such as SFT servers (mirrored servers) but how
effective they are for Access back ends I don't know, I've no experience
of them so can't comment on how regular they replicate themselves.

Trouble with hardware based fault tolerance such as mirroring is that
any software faults are duplicated as well, rendering the mirror as
useless as the original.

As others have said, not a lot you can do in Access to mirror the
database in real time except write a lot of code to do it. I generally
use SQL Server for back ends nowadays and since version 7.0 I find it
nigh on impossible to break a database in any way, even by powering down
a server mid transaction, it either rolls forward or rolls back the
transactions in progress upon next power up, it's extremely robust.

--

\\\\\\
\\ \\ Windows is searching
\ \ For your sig.
\ \ Please Wait.
\__\

[Bernard Peek]

In message <SX**********************@ursa-nb00s0.nbnet.nb.ca>, GGerard
<gg*****@nbnet.nb.ca> writes

Hello

Does anyone know if there's a way to mirror data from a backend database to
a second database?

There's no simple software solution using Access. You could do it with
some coding.

You may be able to implement a RAID solution, how you do that will
depend on your hardware and operating system.

If you were using SQL Server, MySQL, Oracle or something similar as your
back-end database you could use replication.

--
Bernard Peek
London, UK. DBA, Manager, Trainer & Author. Will work for money.

[Jack MacDonald]

You could use Access' Replication, and use a timer on a hidden form to
synchronize the data on a specified schedule (e.g. every 5 minutes or
so...)

On Mon, 06 Sep 2004 01:20:50 GMT, "GGerard" <gg*****@nbnet.nb.ca>
wrote:

Hello

Does anyone know if there's a way to mirror data from a backend database to
a second database?

Example: When writing data to one database it would mirror the data in a
second database for backup
and then if anything should happen to the first database the user could
switch to the second backup database.

I can see it done be writing a lot of code but is there a way that it could
be done automatically.

Thanks
G.Gerard

**********************
ja**************@telusTELUS.net
remove uppercase letters for true email
http://www.geocities.com/jacksonmacd/ for info on MS Access security

[David W. Fenton]

Jack MacDonald <ja**************@telus.net> wrote in
news:23********************************@4ax.com:

You could use Access' Replication, and use a timer on a hidden
form to synchronize the data on a specified schedule (e.g. every 5
minutes or so...)

Or you could use the synchronizer that comes with the developer
tools and MichKa's TSI Synchronizer (which provides an interface to
a lot of functionality that is otherwise not exposed) and schedule
the synchs that way, so they'd happen independent of a perticular
front end being opened.

The Replication Manager scheduling interface allows a minimum
sheduled synch interval of 15 minutes.

But I'm having a really hard time conceiving of an application where
Jet would be an appropriate data store that would need higher
granularity than that.

Indeed, I think the whole scheme of mirroring is probably a mistake
-- if you really need that kind of reliability, Jet is the wrong
tool. And if you're trying to work around corruption issues, then
you should solve those problems instead of multiplying your problems
by introducing more code and more tasks that could fail.

One caveat for scheduled synchs in a replicated database: make sure
that all your memo fields are unbound, because if a scheduled synch
occurs while a memo is being edited, you can corrupt the source MDB.

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc