The only problem with using Access for a web application is that it isnt
designed to handle simultaneous accesses. And that's what most web
applications require.If you have multiple requests on Access, it will
queue the requests and handle them one at a time. In some applications,
that's not a problem. On a desktop app, for example, it's not a problem.
On a low-traffic site, it's not a problem. On a web site where it's only
occasionally used, it's not a problem.
I've used Access several times on web sites.First I used it because I
didnt know any better.Then switched to SQLServer and saw my web site
performance improve markedly. Next I used it as a once-a-day method
of getting client information into my web site sqlserver database. My
client understood Office apps, but didnt want to install SQLServer locally
and learn how to update his web site through that. He updates his Access
database, uploads it, and the web site has a twice-daily task where it
opens the latest Access database, reads in data, and updates the
SQLServer database.It's worked flawlessly for about 18months now, and
the client's happy cos he didnt have to learn anything new.
Another application that worked fine for me was using Access as a link to
the client's MYOB database. I set up Access as a DSN for ColdFusion and
Access links to the MYOB database. Daily, the web application updates its
customer database with the latest data in the MYOB database.
These apps work reliably in a web environment, but with the proviso they
dont have to handle multiple simultaneous requests.You can use it for
web apps, but because it only handles one request at a time, your higher
traffic times will be affected by the performance hit of the queueing.
Also there's a strong risk of data being corrupted in that moment when
there are many requests queued.
As always, use the right tools for the job. Access is a terrific tool in
the right situation.
Cheers
Mike Kear
Windsor, NSW, Australia
Adobe Certified Advanced ColdFusion Developer
AFP Webworks
http://afpwebworks.com
ColdFusion 9 Enterprise, PHP, ASP, ASP.NET hosting from AUD$15/month
On Sun, Apr 29, 2012 at 2:46 AM, Roger Austin raust...@nc.rr.com wrote:
On 4/28/2012 9:18 AM, Raymond Camden wrote:
I spoke to a guy yesterday who still has several (old) clients using
Access. It works fine for them so they haven't seen a need to change.
I used to run DeathClock.com on it (4M views per month), but I cached
the hell out of -everything- I did. I still think Access had the
easiest way to create tables. No visual editor I've used yet has come
close - even Aqua Data Studio.
I sort of cringe when people bad mouth Access. I made a lot of money
using Access as a backend with CF 1.5 - 3.1 in the old days. I agree
100% on the interface, they did a great job. I don't use it for the
backend DBs now, but we really shouldn't hammer on older tech since
that is where the ideas of our current systems were fleshed out.
One of the best uses of the newest Access is to link to SQL Server
tables for now technical people. I help some people get started who
know little about relational databases and end up doing some fairly
sophisticated things eventually. The SQL view really helps people
learn to query databases.
--
LinkedIn: http://www.linkedin.com/pub/8/a4/60
Twitter: http://twitter.com/RogerTheGeek
Google+: https://plus.google.com/117357905892731200369
~|
Order the Adobe Coldfusion Anthology now!
http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion
Archive:
http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:350876
Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm
Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
