sqlite

sometimes i start the morning with a particular objective in mind, and through frustration or the inability to find the information i need end up where i started.

the last few weeks i've been  using visual studio express c# edition . i know i've complained about .net before, but that was when i was using win2k and very reluctant to screw up an already working os by a failed .net install. of course xp doesn't have this problem as it's already part of the os.

part of the requirement for the vs c# is sql server express edition, and so yesterday morning i had the brilliant idea of  transferring over my access2k2 book database to sql server. the only frontend applications i could find were database managers with the  actual database stuff done through sql statements. i'm reasonably competent with sql but for quick updates that's not efficient.

and sql express is not exactly portable, so i started looking at sqlite which IS portable.it's the backend db that popfile uses so it's robust. same problem: all the applications fell into the category of db managers.

i googled for hours, installing various mssql/sqlite applications i could find, but no luck..

i came to the conclusion that both sql server and sqlite were aimed at programmers and NOT the end user. which is fine in itself, except that no programmers have cranked out any database applications for the end user.

for now i'm still using openoffice's base. it's a little bit of overkill. right now my book database is a flat file that i could easily export to csv and just use a text editor. i have other plans for it, and the db paradigm is the obvious way to go for the information i have.

as per usual when the internet world is lacking the once piece of software i could make use of, i end up writing my own database program...probably based on sqlite or mysql to keep it portable. last time i had to do this, the result was tkblog :)

Powered by Qumana