T
Todd
I was wondering if anyone could help me with an issue I am having with a
data access page and a MDE database file residing on a network server.
We have multiple users adding records into the MDE file (one table) which
has a primary key of an autosequence number (sequential).
From time to time, I see records disappear and the sequence starts again
from the last existing record when new records are added.
The DAP is set to Data Entry=Yes and only allows new records to be added.
Is this due to the DAP locking the database while a user is adding a record
and if they leave the IE window open, anything new added after may not
“stick�
Or could this be related to different access versions being used across the
network?
I have tried many different settings in access and the DAP, but still see
records disappearing.
Any help would be greatly appreciated.
The first screen looks up the data via DB2 ODBC and passes all fields using
a cookie to the second page to add the record and prompt for more info.
It then sends an email based on the drop down option chosen by the user.
Also, many times it will assign a tracking ID (autosequence) of 1 or 4 and
not assign a valid one (the table is currently on record 588)
data access page and a MDE database file residing on a network server.
We have multiple users adding records into the MDE file (one table) which
has a primary key of an autosequence number (sequential).
From time to time, I see records disappear and the sequence starts again
from the last existing record when new records are added.
The DAP is set to Data Entry=Yes and only allows new records to be added.
Is this due to the DAP locking the database while a user is adding a record
and if they leave the IE window open, anything new added after may not
“stick�
Or could this be related to different access versions being used across the
network?
I have tried many different settings in access and the DAP, but still see
records disappearing.
Any help would be greatly appreciated.
The first screen looks up the data via DB2 ODBC and passes all fields using
a cookie to the second page to add the record and prompt for more info.
It then sends an email based on the drop down option chosen by the user.
Also, many times it will assign a tracking ID (autosequence) of 1 or 4 and
not assign a valid one (the table is currently on record 588)