Microsoft Access
Jun. 25th, 2007 01:37 pm![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
sorrowmonkeyAs an experienced (i.e. screwed by every vendor) IT professional, I have certain opinions of database products. I think almost every product out there has an appropriate use, even if sometimes that use is just to provide material to fill the trash can. It follows that I can be heard saying things like, "SQL Server 2005 has really impressed me: it's now almost like a real database!"
At this point, I'd like to say that there are perfectly appropriate uses of Microsoft Access out there in the world. If you need a database to store inventory for your family store, stamp collection, or "little black book", Access provides a handy combination of user interface tools and database functionality. It's not for me, but I recognize that you can't pay $50,000 for an Oracle license to keep track of your stockpile of knitting yarn.
However, you should never use Access as the primary front-end to your enterprise application. Once you are linking together multiple Access databases (on different versions) to control your SQL Server 2005 data processing, you have screwed up. One of these three incestuous Access databases is corrupted, or perhaps all three. The reality, though, is that now I've got a pile of Microsoft crap here that doesn't work.
Nice.
At this point, I'd like to say that there are perfectly appropriate uses of Microsoft Access out there in the world. If you need a database to store inventory for your family store, stamp collection, or "little black book", Access provides a handy combination of user interface tools and database functionality. It's not for me, but I recognize that you can't pay $50,000 for an Oracle license to keep track of your stockpile of knitting yarn.
However, you should never use Access as the primary front-end to your enterprise application. Once you are linking together multiple Access databases (on different versions) to control your SQL Server 2005 data processing, you have screwed up. One of these three incestuous Access databases is corrupted, or perhaps all three. The reality, though, is that now I've got a pile of Microsoft crap here that doesn't work.
Nice.
![[identity profile]](https://www.dreamwidth.org/img/silk/identity/openid.png){kind=small}
no subject
Date: 2007-06-25 08:10 pm (UTC)Linked, incestuous, Access DBs and their *bad touch*... bwhahaha.
You'll get 'em sorted out and it will be a ton of work - that will suck, you really do have my sympathies.
no subject
Date: 2007-06-25 08:14 pm (UTC)no subject
Date: 2007-06-25 08:16 pm (UTC)However, it would cost FAR more to "fix" it in such a way that it stays on the Access platform. I will convert it to "marble-machine" for free.