🚀 go-pugleaf

In article <talrozen.5.31097BDA@math.tau.ac.il>,
   talrozen@math.tau.ac.il (Tal Rozenberger) wrote:
>What solution of fault tolerance to use (VINCA, SFT II, SFT III, Double Take 
>....) ?
>Can I write the application in MS-ACCESS ? What configuration does it need ?
>How to make sure to have data integrity ?
>How can I catch network error in MS-ACCESS ?
>What database to use ?
>Can I backup to tape while files (database) is opened ?
>How to lock the user to use only the application, and not letting him do 
>anything else ?
>What database support two-phase commit ?


I don't have all the answers to your questions, but have been playing with 
Access and Microsoft's SQL server lately.  Access works basically out of the 
box for File server/client database stuff.  There is also a complier so that 
you can give the enduser a standalone frontend and therefore limit what access 
they have to your database.  So that cares for a couple of your requirements.

If you visit Microsoft's web site and look around there a couple of articles 
on upsizing an Access database from fileserver/client to SQL.  SQL is 
basically an older product that needs backwards compatiblity with other front 
ends and has some special rules for using it.  If you are considering SQL as a 
backend, it would pay to find out the rules for upsizing BEFORE you start 
using Access.  Access does make it quite easy to upsize.

SQL allows you to datadump the data tables and then you can back up those and 
have a solid backup.  And since MS's SQL would reside on a WinNT server, there 
are avenues for tape backup there also.  Sounds like you might want to 
investigate this avenue more for your specific needs.

Lyle