E
edself
I've created a number of access databases and never had any problems with
navigation buttons until now.
I have a form which allows viewing of approximately 1000 records of data.
Recently, I noticed that I can use the next record and last record portions
of the standard Access navigation bar without problems. The previous record
button also works fine. However, if I use the First record navigation
button, or if I type in a new record number that goes back MORE THAN one
record, Access will crash almost every time.
Other forms in my database do not seem to have this problem. In fact, even
the form that is crashing will work fine if I specify a filter that reduces
the number of records from around a thousand down to a handful of records.
In the filtered case, the First Record navigation bar works fine.
Have you ever heard of such a problem? This is bizarre.
navigation buttons until now.
I have a form which allows viewing of approximately 1000 records of data.
Recently, I noticed that I can use the next record and last record portions
of the standard Access navigation bar without problems. The previous record
button also works fine. However, if I use the First record navigation
button, or if I type in a new record number that goes back MORE THAN one
record, Access will crash almost every time.
Other forms in my database do not seem to have this problem. In fact, even
the form that is crashing will work fine if I specify a filter that reduces
the number of records from around a thousand down to a handful of records.
In the filtered case, the First Record navigation bar works fine.
Have you ever heard of such a problem? This is bizarre.