> I refer you to his original question: "Can it handle simultaneous access
> from many users or is SQL better for this".
>
> His "problem" was many users, not a small db.
His problem was actually that users were not getting validated correctly,
which IMHO probably isn't an error you would likely get due to too many
simultaneous users.
I know that this has been beaten to death here, but Access will work for
many sites. The question of what strength of DB you should use cannot be
answered by anyone but the app itself. Test it with both. Try to determine
the point at which it will break on Access. The truth is that I hate
Access, but a really well designed site with plenty of good query caching
and such can handle an enormous load of traffic. It all has to do with the
way the app's designed. If it makes tons of DB calls, access will break
under a smaller load. If most of the data is cached in app vars or cached
queries, it takes a much higher load to break it.
-Cameron
--------------------
Cameron Childress
ElliptIQ Inc.
p.770.460.7277.232
f.770.460.0963
------------------------------------------------------------------------------
Archives: http://www.mail-archive.com/[email protected]/
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
