What is the future of developing using access?

[Bee]

Hi folks,

I came across a lot of people who think access is a 'crap' way of developing DB because Access has a number of limitations.

I am wondering what everybody here thinks and what is the future of developing using Access?

Cheers,
B

 

[boblarson]

I think it's a great rapid development tool for creating quick, easy to use, applications that do a lot. I think many people have a negative attitude towards Access in that it is easy for people to start building databases that totally suck and they don't know what they are doing so they can come up with some really bad stuff. But, at the same time, I know that I have created some very cool applications that our company uses that didn't need to have a lot of time spent developing, we don't need to have only those who have VB or VB.NET installed to be able to do fixes, and they handle small (relatively) amounts of data well.

Now, if an app looks like it might need to have more power behind it, we then create a SQL Server based backend and may, or may not, move the front end to a VB/VB.NET front end. Access is still a great front-end tool as well.

I think another reason why people, especially network admins, are down on Access is that it is really meant to be a small business tool that runs on a single computer and not via a network. Yes, it is built to go over a network, but as far as the processing and data flow goes it can, if not built properly, bog down the system and also generate lots of problems for users with corruption issues. But, most of that can be gotten around if you know what you're doing.

Also, just as a side note, I do like the new Access 2007, but it is definitely taking a bit to get used to.

 

[mhartman]

Hello:
On those kind of people, its really a sour grapes type of thing. Amen to what Bob said above.

Regards
Mark

 

[Pat Hartman]

Here's a link to an article that you might want to pass on to the nay-sayers:

http://fmsinc.com/tpapers/genaccess/DBOD.asp

In it Luke Chung, the owner of FMS Inc. talks about Access' place in the organization.

PS, while you're there, take a look at the other articles.

 

[Len Boorman]

Those that do not understand Access or indeed Relational Databases are often those that Produce crap applications.

The ROI withAccess far exceeds that of any other RDBMS.

Yes there are limitations but in many organisations the number of concurrent users is frequently very small for a large number of applications.

The amount of data that can be addressed ithin access is relatively small compared with others but with a correctly normalised application it is still a hige amount of data.

There is a feeling in my company that what I do is a Black Art, In fact it is nothing of the sort. The level of training and knowledge required to produce a good application is much higher that say Excel and because you get Access along with Excel etc the belief is that only minimal training is required. This is where Management have it wrong.

The thought that paying big bucks for Oracle and big bucks for the support team is considered to be essential for a good application. This is utter rubbish but of course it is only those that "know" who are aware of this falsehood.

Okay so something like an ERP willneed omething bigger that Access behind it but what do we do with Access

Quality Management (Audits, Product, MEDA, FRACAS)
Serial Number Management
MSG3 Analysis
FMECA Analysis
Technical Manual Distribution
Engineering Change Management
Spare Engineering
These is a few to be going on with

What can you do with Access. Basically anything you can do with any other RDBMS sugject to size and concurrent user limitations

How much data can you get into Gb or 2. Answer Lots. You can use hyperlinks to access lots more dat.

People have closed minds. They need to opentheir minds and learn

L

 

[dan-cat]

Access is a file based DBMS. It's that simple. It's quick to learn and if you keep your concurrent users down to a small number and your required storage space below 2GB then it's a great way to cut your teeth for software design.

However I will say this:

When it comes to internet design it falls woefully short.

1) Support for XML/Webservices is limited
2) Security set-up is limited (the whole .mdb file needs appropriate read/write permissions)
3) Concurrent connections can cause corruptions (a big deal with a web-based front-end)
4) No way of translating an access web form to HTML
5) MS are ploughing their energies into the disconnected data model (XML, asp.net etc etc..) Access prefers forms-bound technology which can hit your network hard.
6) There is little encouragement to think in terms of object-orientation. The basis of the most exciting Microsoft development technology: .net

I can guarantee you that the MS development budget for .net far exceeds the one for VBA

Here's a good article to explain further, what I think, MS eventually has in store for the Office development environment:

http://www.devx.com/OfficeProDev/Article/28088

All of this on top of the fact that MS now offers an "express" version of SQL server for free? It doesn't take too much to work out which path Microsoft are encouraging you to take.

 

[Fifty2One]

the only problem i have ever had with access is the same problem i have had with everything from MS: their support documentation sux because it seems that their offering of help is based on the idea that people have used the previous version of MSwhatever...

...the best part of the above flame is that there are forums like this to help bail people out...

 

[mamandeno]

I find with access I am the limitation not the software.

I am no computer propgrammer, but I have been able to build myself some great little databases to do various bits and pecies ythat used to take me ages. Recently completed an a database for all our in house training records, which cost way less than an off the shelf package and suits our business better. (made possible by a number of tips from generous contributors to this website).

I also have a more complex access database that can predict when farmed shellfish will have grown to harvest size, based on their size, date of seeding, time of year and local growth characterisitics, all defined in a custom function.

This is a complex equation and it predicts very well.

Now that is some good functionality, for a cheap peices of software.

Me thinks access good, especially for novices.