Access versus The Rest

[Chinde]

Not exactly sure where this should be posted, but is it possible to request an insight article??

The drive of which would be the main differences between the DB types.Like Access, MySQL or SQL Server, what would each one be used for, and maybe the a little bit on how a simple DB would work with each??

[NeoPa]

Insight articles are normally done by people when they have something they want to share. This is often triggered by finding a number of questions with the same fundamental requirement.

While there's nothing invalid about such a request, I wouldn't expect much in the way of a response.

Frankly, I fail to see the need for such a request. A simple question would do (with normal responses). If this is something that's been requested of you, then that is not something you should be asking. We answer questions where we can, but we're not a free resource to do work for members.

I'm not assuming that's why you're asking this. Just explaining the situation.

[Chinde]

Thanks for making it clear.

I understand your point, but maybe in myself flagging this up an expert here may realise that the article I've suggested is exactly the type of article they would like to write, who knows.

I have to admit that being a novice in the world of databasing the issues I outlined can be quite confusing and I have often heard people taking about the limitations of access versus brand x.

Finally, if anyone knows of such an article please point me in the right direction as I would love to learn more.

Thank you.

[NeoPa]

@Chinde
Very true. Let's see if anyone feels inspired. It's not a bad idea for an article as it happens.

[Krandor]

@Chinde
Here is a start:

Access is easier for newbies. It is possible for someone with almost no database experience to create a simple database application. Unfortunately, those simple applications don't scale well when muliple users are involved.

Access is for small applications with 1 to up to about 10 users connected at the same time. Anything more and it will seriously choke.

MySQL or SQL Server are for more experienced database developers. They can handle millions of records in their tables and potentially hundreds of concurrent users. There are lots more powerful features to manipulate and present data that are not available in Access.

[Chinde]

Thank you that is very helpful, just to know the scope of an access application is very useful. It has put my mind at rest that I am using the right stuff for my relatively small needs. Do you know of any good websites to have a look at to get me going in the direction of MySQL or SQL server?? Just for my own curiosity really.

Again thank you.

[MrDeej]

@Krandor
Nr1. I have runned an Access application with 20 concurrent users without problem. I mainly rely on ADO programming and use unbound forms and objects for all information input/output.

Nr 2. SQL servers can be used trough access with almost no difference from normal Access. I use a combined Access table and SQL tables in my database and the programming experience is the same after the SQL tables is created and connected

[Chinde]

Nr 2. SQL servers can be used trough access with almost no difference from normal Access. I use a combined Access table and SQL tables in my database and the programming experience is the same after the SQL tables is created and connected

So what you are saying is that if my database needs to grow I could still keep all of my hard work on the access FE VBA coding and all and just link to a different BE which could be on the SQL Server??

[MrDeej]

@Chinde
yes. SQL tables function the same as Access tables when they are linked up. The difference is when you are going to make changes to field formatting and field types and so on

[Chinde]

Excellent. Thank you all, I feel much happier just building an access based DB, which, if need be can be scaled up easily.

I guess that this should have been my question originally.