by a Thinker, Sailor, Blogger, Irreverent Guy from Madras

Acces vs SQL


I've always said that database applications should not be in MS Access.  Access should be used only for some self-help / DIY home use like a database of CD collection, Books loaned, returned and lost, or tracking price of whiskey.
;-/

If you start using it for any fairly large uses, especially over LAN and on fairly old (<1GHz / <512MB) PCs, you're definitely asking for trouble.  It just sags like a old hag.  And if the db grows to more than a 1000 transactions with 1000 or more details to choose from ... it becomes that old joke:

about old women and Siberia -
no one wants to visit them!

DBs should always be in SQL.  The reason why progies still insist on Access must be because they can write a VB frontend and sell it for several thousand bucks. 

Q: And why VB and not in C++? 
A: Because that's their skill level, dumbo.

With OpenOffice 3.1.+ and SQL connector, the time is here to downsize those dummies or for someone to make a couple of thousand quick bucks (using OOo and MySQL).

Even the Election Commission of India has realised its folly and has arranged to change from MS Access to MS SQL (??!!??)  I don't know why they did not migrate to MySQL.  But at least a change, even though just a small one, as reported in The Hindu

 — migration of electoral rolls database from MS (Microsoft) Access to MS SQL (Structured Query Language) Server. This would improve search capabilities and analytical process. [For example, a voter’s name can be searched across parts of the rolls, constituencies and districts.]


No comments:

Post a Comment

Support - Donate

Your Blog is

Donate thro ECWID

Contact Form