S
Scoop
I have an order entry database that I have spent months developing.
It's not perfect but functionally speaking, it's good enough for
production. Especially when compared to what it is replacing.
I have been careful to follow "best practices" as I understand them and
have been good at maintaining consistent naming conventions, etc.
There is definately room for improvement as a lot of the forms, code,
and other aspects of the database have been migrated from the old
database but I have been able to address the fundamental problems
associated with the data structure.
That said, there is only one thing preventing me from going live with
this database. On my main order entry form (the core user interface in
the database), I have subforms for customer addresses, order details,
and payments. When entering orders, we frequently start getting the
"Not a valid bookmark" error. Here is all the background information I
can think to provide as well as what I've observed and what I've done
to try to resolve the error:
- The error is always associated with the "Payment" subform
- The error usually starts after 20-30 new orders have been placed,
though we did get through one day of ~400 orders without the error
occuring. Once it starts, occuring, it doesn't stop
- The database is split...front end mde/back end tables (lookup tables
are stored locally)
- Access/Jet versions shouldn't be an issue...everyone is using Access
2003 with all the same patches, etc. All workstations have been built
from a standard WinXP image and are nearly identical
- The network is rock solid and fast
- As far as I can tell, virus scanners are not an issue
- I've read other posts that suggest data corruption but I don't
experience many of the problems others describe (e.g. if I manually
browse/sort/query the data in the "Transactions" table that my subform
is bound to, I don't encounter any 'obviously' corrupt records)
- There are approximately 320MB of data with roughly 250,000 customers,
400,000 orders, and 600,000 order line items in the database that is
populated initially by an import routine which I have run over and over
again, esentially building all the data up from scratch
- I have tried importing all of the objects/data from both the front
end and back end into new files
Nothing seems to be working and I'm at a loss for what to try next.
Does anyone have any suggestions? This is a big project and I really
need to get this resolved. Any ideas/help is greatly appreciated.
It's not perfect but functionally speaking, it's good enough for
production. Especially when compared to what it is replacing.
I have been careful to follow "best practices" as I understand them and
have been good at maintaining consistent naming conventions, etc.
There is definately room for improvement as a lot of the forms, code,
and other aspects of the database have been migrated from the old
database but I have been able to address the fundamental problems
associated with the data structure.
That said, there is only one thing preventing me from going live with
this database. On my main order entry form (the core user interface in
the database), I have subforms for customer addresses, order details,
and payments. When entering orders, we frequently start getting the
"Not a valid bookmark" error. Here is all the background information I
can think to provide as well as what I've observed and what I've done
to try to resolve the error:
- The error is always associated with the "Payment" subform
- The error usually starts after 20-30 new orders have been placed,
though we did get through one day of ~400 orders without the error
occuring. Once it starts, occuring, it doesn't stop
- The database is split...front end mde/back end tables (lookup tables
are stored locally)
- Access/Jet versions shouldn't be an issue...everyone is using Access
2003 with all the same patches, etc. All workstations have been built
from a standard WinXP image and are nearly identical
- The network is rock solid and fast
- As far as I can tell, virus scanners are not an issue
- I've read other posts that suggest data corruption but I don't
experience many of the problems others describe (e.g. if I manually
browse/sort/query the data in the "Transactions" table that my subform
is bound to, I don't encounter any 'obviously' corrupt records)
- There are approximately 320MB of data with roughly 250,000 customers,
400,000 orders, and 600,000 order line items in the database that is
populated initially by an import routine which I have run over and over
again, esentially building all the data up from scratch
- I have tried importing all of the objects/data from both the front
end and back end into new files
Nothing seems to be working and I'm at a loss for what to try next.
Does anyone have any suggestions? This is a big project and I really
need to get this resolved. Any ideas/help is greatly appreciated.