When I was doing the last-minute testing I found a bug,
I think. I have a formset with ... 12 forms and a couple
of popups. The main form is navigational - users can
skip 1/-1, gotop/bottom, find(indexed), search(locate),
and print/add/edit/delete, as well as quit of course.
This main form has a pageframe with 5 pages. The app
uses customer-supplied table with 173 fields - very
redundant structure, but I can't do anything about it
because it has to sit on our server and be accessible
from any workstation, as well as updateable.

The problem, I think, is in the form-level of default
Refresh() method. What I noticed was totally shocking
at first. When I start the app, - the record pointer is
positioned at the 1st record. I started skipping - went
all the way to the 12th...Then - skipped back to 6th and
started going up to the 12th again. If I press GoBottom,
it goes there alright. I start skipping backwards, - it
skipped 3 records and positioned itself at record #6. I
started skipping forward - it repeated the
above-mentioned loop of going to 12 and going back to 6.
If I start skipping backwards from anywhere over recno#3
it goes to 4, then 3, then...BOF (I DO trap on all
skips for the record position and the table is NOT
ordered at the time of skipping) It does not bomb
because the skip -1 traps the recno and goes top after
disabling the Prior button.

Of course I fixed (temporarily) this weirdness by
capturing the RecNo() before the ThisForm.Refresh() is
issued (thank God I organized the whole thing so that
I issue it only in one place for all forms), then Go
Record to the previously captured recno. Now everything
is cool. I had to do this so awkwardly because I HAD to
release the app for the pilot run.

But why is it doing it? Any ideas?