[AccessD] Old Dog NewTricks

Jim Dettman jimdettman at verizon.net
Fri Jan 14 19:33:58 CST 2011


Dan,

<<3) Reach:  On a LAN, Access performance is great.  On a WAN, Access
performance is infuriating.  >>

  Should point out that JET/ACE was never designed for WAN use and should
never be used over a WAN.

Jim. 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Dan Waters
Sent: Thursday, January 13, 2011 12:30 PM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Old Dog NewTricks

Hi Tony,

These are the significant technical differences that I believe exist (that
affect the user/customer) between a split FE/BE Access app and a
client/server .Net/SQL Server windows forms app:

1) Security: Access login security is only nominal.  I use it at my
customers just so the database knows who is logged in.  If you use Access
login security, you must assume that no one in the company will try to do
something nefarious.  With SQL Server, you can use Windows Authentication,
which is far better.

2) Concurrent User Quantity: With Access, you normally can have perhaps 20
concurrent users before performance begins to slow down.  This could be more
or less depending on exactly how your system is set up.  Some people on this
list have said that they can have over 50 concurrent users on a system where
most users are entering data into forms specified as data entry forms.

3) Reach:  On a LAN, Access performance is great.  On a WAN, Access
performance is infuriating.  

So, for these reasons, you might think that .Net/SQL Server is the way to
go.  But there are many apps where you don't need windows authentication,
your number of concurrent users is limited (or you can create a limit), and
you are on a LAN.  For these situations (perhaps the majority) Access is
excellent.

If you are making a system for your own company, you plan to learn Access
well enough to continue to support it and improve it, and you (will always)
meet the three requirements above, go ahead and use Access.  However, Visual
Studio and the .Net languages have made significant improvements over the
last several revisions (i.e., 'dream language').  Someday you may be asked
to let someone on a WAN log into your system, or someday you may be asked to
'make it work on the internet', and then you'll need to learn .Net anyway.

If you're planning on making systems for your own clients, today you should
start with .Net and SQL Server.

Good Luck!
Dan

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Tony Septav
Sent: Wednesday, January 12, 2011 4:49 PM
To: Access Developers discussion and problem solving
Subject: [AccessD] Old Dog NewTricks

Hey All
Sorry I do not want to start a flame up (I think that is the term),  but 
in my research of VB.Net the conundrum of what are the advantages of my 
using VB.Net to enhance the development of a database application versus 
ACCESS keeps coming up. If you can could you please direct me to 
articles expressing this view or your views pro/con (I am not writing an 
article on this, it is just for my own curiosity) it would greatly be 
appreciated (remember I am a Newbie to VB.Net). If you don't mind, to 
avoid clogging up the user group,  please  EMail me offline. Any 
responses will be greatly appreciated.

Thanks
Tony
-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com


-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com




More information about the AccessD mailing list