G
Guest
Guest
Just for the record, I would like to add that my copy of YIO has not been "unstable" as another has intimated of YIO.
I'm the "another" that you mention.
I'm glad that you have had no problems with the Microsoft Access database. But just in case, the following might be good web sites to bookmark:
Corrupt Microsoft Access MDBs FAQ
and more specifically:
Some Microsoft Access MDB Corruption Symptoms
The Microsoft Access Jet database engine was designed to keep small phone lists and recipes on. It has few if any fault-tolerant features and has a long history of being prone to key-chain and index corruption.
I wouldn't put mission-critical data on it... but if you are only going to have a few hundred up to a couple of thousand records on it and if you have good power protection... a loss of power can really mess up Access... I'm think you will be OK. One suggestion... you might consider rebuilding the .mde every once in a while. Your best protection is to keep a week or two of backups... making one each day. (And test them every once in a while.)
Remember, I'm just one person and while I have many years of experience with Access and many other databases, my advice and opinion is worth what it cost you.
And note... before you hit the "flame" button... this has nothing to do with YIO. I'm sure after all this time YIO is bug-free and stable (i.e. it does not crash or freeze due to a programming problem.) I'm talking about the Access database... which lots and lots of applications use. It is fine for simple home or small office non-essential record keeping. However you would NOT see any knowledgeable (small or large) business or corporation use Microsoft Access for its mission critical data... they use SQLServer or Oracle or MySQL or Postgres or Sybase or any one of a hundred others.
Al