I suggest we don't pick Access/Jet MDB as our shining example of SQLite's future
Borland's old, dead, and gone Paradox was Access' main reason to come into existence. Inspire of outliving Paradox, only because of marketing reasons, Access has never been able to leapfrog or even measure up to old Paradox's last few gasps, IMHO. This periodic "need" for vast "improvements" always seems to end up proposing breaking the whole reason SQLite exists and why it addresses its chosen segment of the market so wonderfully. If someone needs table or row level locking in a multi-user environment, selecting SQLite is like trying to take that old '57 fuel injected, ultra lite Corvette and use it for a fully tricked out hearse. Sounds to me like a job for "Monster Garage" rather than CVS SQLite :-) Fred > -----Original Message----- > From: Mikey C [mailto:[EMAIL PROTECTED] > Sent: Friday, June 16, 2006 10:39 AM > To: sqlite-users@sqlite.org > Subject: Re: [sqlite] SQLite Vs VistaDB - Comparison ??? > > > > Okay I know very little about these things, but the fact that > Access/JET MDB > files are serverless (it's just a bunch of Windows dll's) in > the same way as > SQLite, and that JET implements row and table level locking > means I guess it > is possible. ...
