> Me too, but they are mostly urban legends. > Like for instance "Access is really bad when serving many > users at the same time". > > This affirmation just does not make sense for WEB applications. > This may be true for an Access application on a lan, but > since when used with CF there is always only ONE user: > coldFusion, it does not apply.
Unfortunately, those aren't urban legends at all. While you might only have one login being used, what Access has problems with is concurrency. This has nothing to do with the number of users, and everything to do with the number of requests. Access locks the entire table when you update a single record in that table! That obviously won't scale well. Also, Access databases grow in file size as you add records, but don't shrink or reuse space as you delete records. So, a volatile table (like, say, one holding CF client variables) will cause the Access database to keep growing and growing, even if the number of records doesn't grow. I encountered one server environment where the Access database was around 2 GB, and it had maybe two hundred records in it. It was ... very ... sl-o-o-w. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ Fig Leaf Software provides the highest caliber vendor-authorized instruction at our training centers in Washington DC, Atlanta, Chicago, Baltimore, Northern Virginia, or on-site at your location. Visit http://training.figleaf.com/ for more information! This email has been processed by SmoothZap - www.smoothwall.net ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Macromedia ColdFusion MX7 Upgrade to MX7 & experience time-saving features, more productivity. http://www.adobe.com/products/coldfusion?sdid=RVJW Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:275820 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
