|
Leo, why didn't you behave and put these relevant comments in your first post?
The answer is empirical research since version 1.0.
You seem to have the faulty assumption that Access/JET databases turns corrupt all the time. I guess you have read the word "prevent" in the title of the article as if the 10 advices given are not followed, any Access/JET database will corrupt. The title is not mine.
However, that is not the case, on the contrary. They don't:
<quote>
.. Access/JET does run mission critical applications around the world wether you like it or not - and at just about zero cost. We have clients here running different applications with Access/JET as the backend database experiencing 0 (zero) failures for more than 10 years. This is a fact.
</quote>
But - as with any other technology/software - issues may be experienced, and to keep these at zero or at least at a minimum some guidelines exist of which the 10 mentioned are some.
Have in mind too, that Access (the application) is used by many normal or super users which don't have much experience as db admins. It is easy for pros like me and (I guess) you to point fingers playing the clever guy. You gain much more by helping and guiding.
As for choosing another RDBM, you are right, indeed when so many high-quality server based engines are available for free like FireBird, PostgeSQL, MySQL, MaxDB, and (with their limitations) the "express" versions of DB2, Oracle, and SQL Server, even though these often require skilled maintenance:
<quote>
.. we may very well advice clients to use some other database for their specific task if we can see Access/JET won't fit the bill.
</quote>
In many cases, though, Access/JET as an backend database will fulfill the task, indeed for single user applications. Even though, MS pushes the use of SQL Server 3.5 Compact Edition which is a file based database very much like JET but for one concurrent user only. It has only one thing in common with its likely named server based big brothers, the SQL language, or rather a subset of the language. This means that you can design an application with the CE as the backend, and if or when you feel the need, the data can easily be moved to a server based engine, and the application can use this with minimal tweaking. Not a bad combo.
So - for databases as for so much else - one tool doesn't fit all purposes.
/gustav
 |