> ONE user at a time accesses the database:
> ColdFusion is the user. This driver is just as good as the
> Oracle or SQL Server driver.
The driver is only part of the puzzle. There is a hard limit on what Access
can handle (I don't know where it is), but that's not my biggest gripe. The
fact that you have to take the database offline to change it is way more
significant. Sure, performance is important, but as Ray points out, if you
build the code right (and have the RAM and processor cycles on the app
server), you can run amazing load with a POS backend, regardless of the
actual storage engine. Backups are also problematic, because you have to
deal with the file as a whole, rather than individual tables, or the like.
Also, you have to have it local on the CF server, as far as I know, which
can lead to problems.
I can't say I've ever had major problems with Access, but at the same time,
I'll never use it for a site unless I have no other choice.
Cheers,
barneyb
> -----Original Message-----
> From: Claude Schneegans [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, May 25, 2004 12:55 PM
> To: CF-Talk
> Subject: Re: MS Access as a backend database
>
> >>this isn't exactly true. When
> I use to run Death Clock, I would get 3-4.5 million hits a month.
>
> I will vouch this statement.
> The "user limit curse" of Access is pure urban legend.
> The PROGRAM Acces installed in a lan does have a limit, but
> as far as CF is concerned,
> the Access program is not used nor is installed on the server.
>
> Only the ODBC driver is used on a flat .mdb file, and only
> ONE user at a time accesses the database:
> ColdFusion is the user. This driver is just as good as the
> Oracle or SQL Server driver.
>
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
