[AccessD] Learning .Net

Well I know that feeling.  You get accustomed to a certain system, and
it's hard to see the advantages in other systems.

Using both, I do see advantages and disadvantages both ways.  For a
'quick' web based system, I stick with Access.  If a system even has a
remote possibility of requiring an interface that is Non-web, I will go
with SQL Server.  After that, it's a matter of size considerations, and
if I will need SQL Server capabilities.

Drew

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Jim Lawrence
Sent: Tuesday, June 23, 2009 5:27 PM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Learning .Net

Agreed... Drew. It may be that I have just used MS SQL for too much and
Access MDB too little. ;-)

Jim

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Drew Wutka
Sent: Tuesday, June 23, 2009 3:06 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Learning .Net

We'll just have to agree to disagree here Jim.  While it is free to use
SQL Express, and it does have advantages over JET and an .mdb, there are
still advantages the other way:

It's an .mdb, you don't need Access installed to use it.  A web server
with ASP and ADO is all you need.  It's a single file, you can copy,
swap, or change the .mdb with just that file.  (No detaching and
reattaching of a database).  It's less resource intensive....more
features, more resources.  Jet runs great on a local machine, which is
what happens when you put an .mdb on a webserver, it's local.
Development is easier with all the nifty Access tools.  Access' query
builder is way easier to use then Enterprise manager's query builder.

Again, not saying there aren't advantages the other way, just saying
that I don't think you can truly say one situation is better in all
cases.

Drew
The information contained in this transmission is intended only for the person or entity 
to which it is addressed and may contain II-VI Proprietary and/or II-VI Business 
Sensitive material. If you are not the intended recipient, please contact the sender 
immediately and destroy the material in its entirety, whether electronic or hard copy. 
You are notified that any review, retransmission, copying, disclosure, dissemination, 
or other use of, or taking of any action in reliance upon this information by persons 
or entities other than the intended recipient is prohibited.