> This is one of the prime reasons not to use an Access or file-based
> database. If you use SQL Server, or any client server DB, you simply point
> the new DSN to the new SQL server. Both sites can now use the same
> database. No hassles. No updates. No "merging" of data.
Here's a few other "prime" reasons;
Access only does Table Locking, SQL Server has record locking
Access has a 50 concurrent user limit before it crashes - SQL Server has no
theoretical limit
Access has no native "get the identity of the current record" function
(AFAIK)
Access doesn't have Stored Procedures
Access is a bloody Desktop application! Just the part of SQL Server that
says "Server" should give some hint as to why it's better for servers <g>
I could go on, but I won't
Philip Arnold
Director
Certified ColdFusion Developer
ASP Multimedia Limited
T: +44 (0)20 8680 1133
"Websites for the real world"
**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.
**********************************************************************
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
