D
Donald Tilley
We have a commerical voice response system application
that uses MS-Access 2000 to keep track of the status of
each of the phone lines coming into the Server (e.g.
busy, available). A log table is updated each time a
call comes in to reflect the busy status. There is one
record in the log table for each phone line in the
system. As more lines are added to the system we've been
seeing record locking conflicts arise from time to time.
Has anyone dealt with optimizing the record-locking
parameters in Access in such a way as to avoid these
kinds of conflicts?
Under the database's "Tools", "Options", "Advanced" tab
we have a setting of "Shared" for Default open mode; "No
locks" for Default Record Locking; DDE Refresh is
enabled. For "OLE Timeout" we have a setting of 30
seconds; a "Refresh interval" of 60 seconds ; a "Number
of Update Retries" setting of "2"; "ODBC Refresh
interval" is set to 1500 seconds; and "Update/Retry
interval" is set to 250 miliseconds.
If anyone has a suggestion about "tweaking" these
parameters to minimize record update conflicts between
the records corresponding uniquely to each phone line,
I'd appreciate hearing from you.
Thanks very much,
Don Tilley
that uses MS-Access 2000 to keep track of the status of
each of the phone lines coming into the Server (e.g.
busy, available). A log table is updated each time a
call comes in to reflect the busy status. There is one
record in the log table for each phone line in the
system. As more lines are added to the system we've been
seeing record locking conflicts arise from time to time.
Has anyone dealt with optimizing the record-locking
parameters in Access in such a way as to avoid these
kinds of conflicts?
Under the database's "Tools", "Options", "Advanced" tab
we have a setting of "Shared" for Default open mode; "No
locks" for Default Record Locking; DDE Refresh is
enabled. For "OLE Timeout" we have a setting of 30
seconds; a "Refresh interval" of 60 seconds ; a "Number
of Update Retries" setting of "2"; "ODBC Refresh
interval" is set to 1500 seconds; and "Update/Retry
interval" is set to 250 miliseconds.
If anyone has a suggestion about "tweaking" these
parameters to minimize record update conflicts between
the records corresponding uniquely to each phone line,
I'd appreciate hearing from you.
Thanks very much,
Don Tilley