--- In [email protected], "Glenn B. Lawler" <[EMAIL PROTECTED]> wrote: > > Arsen, > > >Im going to create a DB which have a many tables and records > > (more about 100 000)what kind of DB file you can advice?mdb, paradox or ??? > > Microsoft Access or Paradox files are fine for a single user > desktop application. Neither is a good approach for multiuser > access. Database corruption is common with multiple users. > Paradox has the advantage that tables and indexes are in > separate files in the file system and may be up to (at least) > 2 GB. Older versions of MS Access are limited to 1 GB for > the entire database (all tables). Newer versions increase the > limit to 2 GB, but all char columns are in unicode (2 bytes > per character), the increase is really not significant. Having > everything in a single MDB file is convenient for backing up > and versioning, but the size limitation is very confining. > > There are a number of very good free choices for client-server > RDBMS's: PostgreSQL, MySQL, Firebird are a few. PostgreSQL > and Firebird are fully featured and compete with MS SQL Server. > MySQL is only recently starting to add the features you really > need in an Enterprise class RDBMS (transactions, triggers, and > stored procedures). > > You may want to consider using one of these free client-server > RDBMS's, unless you are sure this is a single user application > only. Even if single user, build something into your app that > makes backup and restore easy for the user to do frequently > because corrupt database files are very common with MDB > and Paradox. > > Glenn Lawler > www.incodesystems.com >
In my experience the only database that is worse than Access is FileMaker. I would not use Paradox - though I like its rigour - because it is no longer supported. For the last 6 years I have been using Firebird because it has events that I can use to make its interface appear much more like a desktop db. It is very snappy and when the application is carefully written it can run over dialup almost like it was on the floor next to me. By carefully written I mean - just retrieve the bits that have changed, only post pieces that your user has changed. I use FIB+ and it will rewrite the post SQL on the fly. hth Mick
