Wortz, Charles
CWortz at tea.state.tx.us
Sat May 17 11:52:30 CDT 2003
Robert, First get off that pier-to-pier network. The first freighter or ocean liner that crashes into one of your piers is going to cause havoc with your network! <grin> Second, besides the other good backup suggestions, you could create a transaction log on another server and write transactions to it. That way you only lose those transactions that were still being written to the transaction log when your db crashed. Charles Wortz Software Development Division Texas Education Agency 1701 N. Congress Ave Austin, TX 78701-1494 512-463-9493 CWortz at tea.state.tx.us -----Original Message----- From: Robert Gracie [mailto:Subscriptions at servicexp.com] Sent: Friday 2003 May 16 19:32 To: Access D Subject: [AccessD] BE, Back Up Question I have been reading of more and more Access BE's corrupting beyond recovery, and Am getting a little concerned. I'm working with a mammoth Access DB, (FE/BE Split) it's a full Business Management System which has around 214 tables in the BE, with a 22Meg Front End. It's been running Ok for about a year, but with a db this complex, I need to find a way to back-Up the BE db every 30 to 60 minutes while users are still in working. How might one go about doing this safely? The BE resides on a Pier-to-Pier network with the "server" running Win2K. Thanks Robert Gracie