Access will handle the file locking internally. The locking scheme is, of
course, dependant on how you setup Access/Jet and what parameters you set on
your connection objects (ie. adLockPessimistic, adLockOptimistic, etc), what
type of recordset (if any) you open, etc etc.
How heavy will the transaction load be? Access works fine in a Web
environment assuming most of your processes are analytical (i.e. lookup,
reporting, etc). If you are going to be doing a LOT of transactions, backup
frequently.
--
Scott McDaniel
CS Computer Software
Visual Basic - Access - Sql Server - ASP
"Scott Bryce" <sb****@singlepoint.net> wrote in message
news:3F**************@singlepoint.net...
I am creating a CGI application in Perl that uses an Access database. It
will be hosted on an NT server. I have used flat file DBMs (tied hashes)
on UNIX servers, but I am not familiar with how Access behaves in a
multi-user environment.
Will I need to use some sort of file locking/semaphore scheme, or does
Access (or the ODBC drivers?) manage conflicts between multiple users? I
want to avoid corruption of data should multiple users attempt to write
to a table/record at the same time.
If a semaphore is not normally needed, under what circumstances should I
consider using one?