Access vs vb.net/ado.net

[John]

Hi

What are the advantages of writing an app in vb.net/ado.net as opposed to MS
Access? I need this to sell the idea to the management.

Many Thanks

Regards

[Miro]

John this is from my point of view - someone who uses dbf's and msaccess tables.

I started writing some dummy apps teaching myself .net and started into using msaccess dbfs.

A couple weeks in - i pulled the plug and started using sql express. ( switched over ).

1. Its more secure once you set up the database on the server.
2. Ms Access seems to be slowely phased out ( if it ever will is another story ), and anything
new / any new books even, teach on ms sql.
3. MS SQL database has settings within it such as rollbacks and other database features you
might want to use or not. -I havnt gotten to this point - and am far off it.

From a personal point - I am very glad I switched to Learning sql express instead of msaccess.

With programming questions... it seems as well more people here already use the sql db than access,
so getting help with code I write, seems to be more people using the same thing.

I am a newbie, i would wait for some more technical answers from the longs, but I like the
new SQL way better than the msaccess.

It just seems to fit properly with .net as well
Miro
John wrote:

Hi

What are the advantages of writing an app in vb.net/ado.net as opposed to MS
Access? I need this to sell the idea to the management.

Many Thanks

Regards

[cfps.Christian]

John wrote:

Hi

What are the advantages of writing an app in vb.net/ado.net as opposed to MS
Access? I need this to sell the idea to the management.

Many Thanks

Regards

I don't think Access has the option but I know one of the big things
in SQL now with the SOX laws in effect is there is a way to record who
changed a row, when they changed it, what they changed it from and
what they changed it to. Creates a paper trail for people that are
trying to get in there and rip off the company.

[=?Utf-8?B?VGVycnk=?=]

While you may not want to jump from Access to SQL server at this point in
time - writing your apps with VB now, will make any furture transition much
easier.
By properly seperating the Data Access Layer (DAL) from the UI, if it became
necessary (or desirable) at some point in time to switch from Access to
something else for any number of reasons (database size, number of concurrent
users etc), the transition would be much easier and cleaner. By doing it
this way now, you will have many more options down the line.

--
Terry
"John" wrote:

Hi

What are the advantages of writing an app in vb.net/ado.net as opposed to MS
Access? I need this to sell the idea to the management.

Many Thanks

Regards

[William Vaughn]

Companies large and small are spending millions moving applications off of
Access/JET. While I use Access, I use it as it's intended (IMHO) as a home
or VERY small business database tool--I use it to maintain the choir roster.
Access forms and reports are generally not transferrable to more serious
paradigms. The JET databases it creates (by default) are not securable, not
saleable and not reliable. I would do some additional research before using
Access/JET in any serious way. Some have made it work but many others have
regretted taking that course.

--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant, Dad, Grandpa
Microsoft MVP
INETA Speaker
www.betav.com
www.betav.com/blog/billva
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
-----------------------------------------------------------------------------------------------------------------------

"Miro" <mi******@beero.netwrote in message
news:47**************@beero.net...

John this is from my point of view - someone who uses dbf's and msaccess
tables.

I started writing some dummy apps teaching myself .net and started into
using msaccess dbfs.

A couple weeks in - i pulled the plug and started using sql express. (
switched over ).

1. Its more secure once you set up the database on the server.
2. Ms Access seems to be slowely phased out ( if it ever will is another
story ), and anything
new / any new books even, teach on ms sql.
3. MS SQL database has settings within it such as rollbacks and other
database features you
might want to use or not. -I havnt gotten to this point - and am far off
it.

From a personal point - I am very glad I switched to Learning sql express
instead of msaccess.

With programming questions... it seems as well more people here already
use the sql db than access,
so getting help with code I write, seems to be more people using the same
thing.

I am a newbie, i would wait for some more technical answers from the
longs, but I like the
new SQL way better than the msaccess.

It just seems to fit properly with .net as well
Miro
John wrote:

>Hi

What are the advantages of writing an app in vb.net/ado.net as opposed to
MS Access? I need this to sell the idea to the management.

Many Thanks

Regards

[Spam Catcher]

"John" <Jo**@nospam.infovis.co.ukwrote in
news:e1*************@TK2MSFTNGP03.phx.gbl:

What are the advantages of writing an app in vb.net/ado.net as opposed
to MS Access? I need this to sell the idea to the management.

You can still use Access as your backend database - it is fully supported
by .NET.

Access is not necessarily a bad choice for small applications - or
applications you don't want to load too many components onto a user's
computer.

It depends what your doing - do you have more details?

[sloan]

The biggest thing is
"Cost of maintenance".

If you plan out a new application decently, the future costs of adding a
feature, making it support more users will be less, then by keep on hacking
onto an existing Access application.

People think software costs are the development costs. WRONG.
The costs are the maintenance costs.

..Net is the now and future of MS development. You don't want to do a VB6
app (from start) ... and you don't want to create an Access Application.

There is much more wealth of knowledge on the internet about .Net
development. This alone is a benefit. When you need to get something to
work, eventually you will find it on the internet with a dotnet application.

If they outvote you, find another job.


"John" <Jo**@nospam.infovis.co.ukwrote in message
news:e1*************@TK2MSFTNGP03.phx.gbl...

Hi

What are the advantages of writing an app in vb.net/ado.net as opposed to
MS Access? I need this to sell the idea to the management.

Many Thanks

Regards

[Jim Rand]

This is not meant as a slight, but if you don't already know the answer to
this question, you are not ready to sell the idea to management.

Moving to .NET is not trivial. The learning curve is incredibly steep. I
must say, however, the results are well worth the journey.

"John" <Jo**@nospam.infovis.co.ukwrote in message
news:e1*************@TK2MSFTNGP03.phx.gbl...

Hi

What are the advantages of writing an app in vb.net/ado.net as opposed to
MS Access? I need this to sell the idea to the management.

Many Thanks

Regards

[Cor Ligthert[MVP]]

>

An MDB file has always been called an "Access database". I'd still call an
MDB file being in Access database format.

However that was not in the thread before you wrote it. There was written
"there is a database, Access" which was nearest to your reply.

Scott is in my idea very correct with his answer. Using Access is more than
using a database, it is a complete enviroment for endusers and developpers
while databases can pretend to be that, however seldom are. Therefore is in
my idea the question not to answer. It relies on what the company wants with
development.

Cor