What back-end database should I use for this project ?

Do you have a question? Post it now! No Registration Necessary.  Now with pictures!

Threaded View
I'm starting to learn Visual Basic. My aim is to develop a small
downloadable application that can store and display contacts. It has to
be small (say 2 mb footprint?).

Q - First, will Visual Basic give me this small footprint ?

Q - What back-end database is advisable (I'm familiar with MySQL),
considering that the tables will be small ?

Basic goal is that the application should be universally downloadable,
installable (on all windows) and must fit in a small footprint.

Q - Or let me ask very broadly - what technologies would *you* use if
you had to develop such an application ?


Re: What back-end database should I use for this project ?

siliconmike@gmail.com wrote in

Quoted text here. Click to load it

I think you are going to get a rather biased answer since you are
posting to a Visual Basic 6.0 and below group. Of course, if you were
posting in one of the dot Net groups they would tell you the bigger the
foot print the better the application, etc. And I'm sure the people in
the MYSQL group will extol MYSQL. Actually, in most instances I would
extol MYSQL.

Having given some acknowledgement to fat obese code and humongous run
time libraries, let me say that having made my living from relatively
small to medium size corporations almost all of them needing rather
unique highly customized database applications I have found the best
development tools available for this is a combination of Visual Basic 6
or Visual Basic 5 as the front end and either ACCESS 97 or ACCESS 2002
as the backend. I think a number of people are going to say ACCESS does
not comfortably support more than 5 users, so, in deference to that tale
of supposed woe, I have found that from 15 to 25 users is not out of the
question provided: 1)    Your database is on the server
2)    Your front end is not on the server. It belongs on the client
machine(s). 3)    Your network cards are high quality and swapped out as
they begin to fail and, last but not least 4)    Your users fall into the
70-10-20 rule. In short, 70% of your user base is in review or look-up
mode. 10% are in the bathroom, on break, chatting and are simply too
lazy to sign off the system and only 20% are heavily engaged in data

If you follow those simple requirements, ACCESS will do just fine as
your database. If you cannot adhere to those guidelines, you would do
well to look further at MYSQL.  

Site Timeline