.Net vs Access

[ions]

Dear Access Experts.


1) Suppose I am pitching to a new client that wants a business system for 4-6 concurrent users over a LAN.

The client is aware that .NET is the most used technology but already has MS access 2007 as part of their office suite.

What arguments do I present to the client to support Access 2007 development with JET/ ACE backend?

The company is positioned for consistent but gradual growth and may have 8 concurrent users in 2 years and up to 12 in 5 years.

Currently the Data is at 60MB and is expected to increase by most 20MB / year.

BTW-when I say concurrent that means X users using the system not necessarly all using the same form.

What is the definition of concurrent in terms of databases? System or Form/Table? At max 3 users will be using the same form and editing the same table.

2) For single user databases with < 100 MB of data is MS Access 2007 the clear choice vs .NET?


Thank you

 

[gemma-the-husky]

why do you need arguments? Access is perfectly acceptable, and its what your customer wants.

 

[ions]

Gemma,

This is a hypothetical question when I approach new clients. In my region (Toronto) .NET is becoming more and more popular and I want to be prepared for the inevitable question.

 

[gemma-the-husky]

I see

for me, one of the main benefits is that Access comes with all the necessary support built in - using .net will give you a portable .exe file, that won't need the user to have access - but will therefore need more programming to achieve the same result - indeed you may not be able to achieve some of the Access functionality.

 

[Desperate]

If size is not an issue, one of the most important question should be "Which one of these will provide better service with minimum problems in future?"
So lets say if you are better at Ms access,it means you will do a better application and provide better support so you should go for it..

 

[Galaxiom]

Access is going to be much faster to develop because it is a database focused development platform with loads of tools specifically for databases such as linked tables and easy bound forms and reports.

The .NET development needs every object and interaction with the back end spelled out and connection to the backend via recordsets.

Access is often maligned by those who don't consider it as a tool for "real" developers. However much of the criticism is actually against the often poor quality of database designs that are possible precisely because Access does allow the inexperienced to produce a database.

Unfortunately if the potential client gets an earful from one of these doubters it can be very difficult to get Access the respect it deserves.

 

[ions]

Thank you for your responses.

Good points Galaxiom.

 

[Simon_MT]

I have even used Access over a WAN via VPN so if your client need not be limited to a single location. It did require a Terminal Server as well but it eliminated the need to totally rewrite the application.

Simon