Take this situation: A Hospital Database containing information on over 800 employees. Which database software would you use? Is Access just as good as mysql?
Printable View
Take this situation: A Hospital Database containing information on over 800 employees. Which database software would you use? Is Access just as good as mysql?
Depends on whether more than 5 people have to access any of the DB at the same time. It also depends on what you are doing with ACCESS. If it's weekly payroll, that is used by different people on different days, it may work, but you have no room for growth. I'd choose SQL Server, or even MSDE (which is free) as it can be acessed by everyone at the same time. MySQL can probably support the task as well.
Access has limits on connections (5 as dglienna said), personally I just prefer MySQL better. But if its for a business, I think you have to pay licensing fees and what not so...
Thanks guys. I have one more question regarding this: Let's say some problems are arising with this database. Sometimes it won't update untill the 2nd time of entering the information. Their is a refresh button but it doesn't work. Sometimes the information will update if you just exit out and come back in.
What's the chances of this being an access programmatical error, or instability due to the number of connections?
Also, is there a way I can find out how many connections are coming into the DB if it's in a Novell workspace?
Access is excellent for standalone databases however, it doesn't fare to well as a database server. In my personal experience if there is more than one connection at any one time you are likely to get problems.
If I were you i would use MySql or MS SQL Server which are purpose built database servers. But don't use access.
P.s: I moved this to the DB development forum - you will probably get some more detailed responses the ;)
How are you doing your database stuff, thru code or controls? Could you post your code and the error that is raised? I would suggest you use transactions also in your codes and before you develop further problems in the future start migrating your database to SQL Server (or MySQL perhaps, I have no experience in it) now. Also, it might help if you would look into the Access Limitation link in my sig.Quote:
Originally Posted by System_Error
Well, I'm not the one that made the database. I just started working there and was a littled shocked that they were using access....Not that I knew the limitations, but I did know that most don't prefer it in a big setting like that. Whoever did the database never gets things right, and always leave a bug or two in the db...Which can usually lead to enter all the information and then it not show up. I don't have the code, and don't know if they will allow me to post it, because they are VERY secretive about the database and won't let any of the information get out.
Do you know of any other reason to migrate from access to sql server other than the number of connections?
By the way, that was a very helpful link.
PS: I can try to explain the problem we are having, but I don't think I can give code. But the dude that did the database was suppose to fix it friday, and I'm hoping he did. Right now I'm interested in the limitations(as your link specified) of access and why it's better to move to sql.
Thanks for the help.
Yap, before you will encounter any future problems because of the limits of Access better find an alternative now. :)