Click to See Complete Forum and Search --> : JDBC, ODBC, Database ...


TrolloC
10-01-2006, 08:41 AM
Hi
I am writing a tiny application.
Currently it is using mysql.

Im wondering whats better to use (mysql, ms access, something else),
for the application to be easier to distribute.
I think installing mysql on every client machine is rather nasty, and using ms access, for example, can be much easier.

But in mysql i can add columns, remove columns, etc to an existing table.
In ms access i dont think i can do that.

What do you think? Which database to use, and is it possible to make some installer that will install my application, my sql, and configure mysql settings (as i did manually on my computer)

Thanks

Khalid Ali
10-01-2006, 11:59 AM
you can add/remove whatever in ms access as well, however ms access will have some serioud limitiations, such as how many concurrent users may be able to make changes to it.
I'd say MySQL is extremely good db for a free 1. So unless you want to go postgres db or oracle, stay with it..:-)

TrolloC
10-01-2006, 04:54 PM
Yeah i'd like to stay with it :) Any idea how ever how i make some installer for it that can configure it as well, like creating user for login, database for using etc?
I want the user to click on .exe file and thats it for him, but i'm not knowledgable about installers etc.

chazzy
10-01-2006, 09:17 PM
i'm a little confused why this isn't a client-server app (typically database driven is client-server).

anyways, you could write a .sql file that would load up necesary users/passwords, structure etc.

jetbrains
10-02-2006, 04:36 AM
Which database to use?
IMO,to your tiny application,EXCEL is the good choice.

Waylander
10-02-2006, 10:47 PM
MySql is a service, I wouldnt want to package it into an installer or make the user install it.

Access sounds fine for what your doing, as its only a file and its much better than excel for this kind of thing. Concurrent access to the database shouldnt be a problem as its just for your application to use. Just be aware that it has a record limit that you dont want to go over.

We still use access on some of the apps we bundle and I would definately prefer to use mysql but its a service and its not really that suited to being bundled with a standard application.

If there isnt alot of data you could just use xml or a dat file.

Waylander.