what is disadvantage of MS Access using as a back end?

Answer 1

Hello,

Some of the things you really need to know....

When you say "disadvantages" in using MS-Access, it depends on "your project scope". Say for example.. using access as backend you can create well structured and best secure with least expensive windows applications for like banks, retail shopes, storing any kind of data where the data is less then 2-gigabytes and so on..... (if some people do not agree upon this, just consider, they dont know to use it in the proper way)

There is specific disadvantage that makes you think "better not use access as backend". Even Oracle and disadvantages compared to MS-SQL and vise versa. So better you please do not look and say the word "disadvantage" and transform this word to as "functionality" and "limitations".

When we are talking about functionality, here also it depends upon your "project scope". If we consider that you are creating a report with lots of data connected with more than 7+ tables, well structured SQL queries and so on,,,, here come the play of writing "Stored Procedure" (hope you know) which only can be served by server type database like MS-SQL. In access you can write up certain level to fetch the data, and they are raw SQL statements, which are parsed in the time of execution, but is server database, they are all parsed and ready to execute. So the execution is much better than compared to access database.

See, these set of points comes out only when you sit and set out your project scope and you have to thing future of the project. So we should not regret later on this part :).

I have created so many applications using ms-access as backend, both in windows and web applications, still now I didn't faced any problem, (they are running from past 7 years). That shows my project scope and it served. So in mycase, I can't use MS-SQL or any other server database to serve my purpose. And even i have some projects with me that there i can't think of ms-access due to the limitations of it.

So, you can't call this as the disadvantage of using ms-access, They are limited to use to certain way for certain purpose, and they are their limitations. We can't expect a car to fly and we can't call it has its disadvantage.

So, all I can say is that, Look to your project scope and look into its future, what it can be later and how data are stored each day. By this you will get a brief idea on what database you can use and functionality will serve your purpose to the best level.

I had lot to say on your question. I am just cutting down the words and giving you a overlay.

Hope this helps.

Answer 2

Access really isn't a backend at all, more of a frontend. Mostly it lives on an individual's machine, not on a server. There are security issues for sure (like the headache of creating user roles) vs. those of the big brothers (e.g. sql server). But the main problem has to do with multiple users of a database and the hassle of creating transactions (and rollback). It's either a hassle of implementing these functions or it doesn't have them. All the big db engines do.

So: small apps, single user (or small number of user) apps, no security worries, you can use Access.

Answer 3

In real life, MS Access is best solution for single user apps. Otherwise, when working with more than 5 users at the same time it becomes unstable or at least problematic.
Don't count much on transactions in Access, and backup often. Power losses mean data loss.

Answer 4

The main disadvantage of using ms-access is it is not as secure as oracle or mysql or pgsql.

Answer 5

MS Access is fine for small-scale operations, but if you need real DB power, it blows.

However, since it is so heavily supported and workable given the .NET platform, for a lot of functions it is not too bad.

Answer 6

The reason Access is only good for smaller applications is that is has a limit to the number of records...10,000 if I remember my schooling correctly.

Answer 7

i'm not even particular I comprehend the question... reward of creating use of them instead of something else? in case you recommend oftentimes, this is because MS get entry to and sq. are databases. the benefits of databases are too massive to record right here. take a verify out relational databases in some searches.

Answer 8

its good for low end accounts but if youre planning on running a mid business database application you should aim for other ones (less lagging or headaches)