Ned said:
ok, thanks, that was easy to fix.
why does it work that way? what am I missing in the way of this
concept? -Ned.
It "sort of" makes sense if you look at how other objects behave.
If you create a query that returns records and which allows new record
insertion then you will get a row of field names, followed by one or more
rows of records, followed by a blank row where a new record can be inserted.
If the same query returns zero existing records then you will get a row of
field names and a blank row for the new record.
Now, if that query is modified to make it read only you will get ONLY the
row of field names and no actual data rows at all.
In a form with three records you can tell by observing the Record Navigation
area that you are either on row 1 of 3, 2 of 3, or 3 of 3. If you navigate
past record 3 to the NEW record position it will indicate that you are now
on record 4 of 4.
Now imagine the form does not permit new rows to be added. You now must be
on either record 1, 2, or 3. Now filter the form so that zero records are
shown. What would the navigation area indicate? That you are on record
zero of zero? The answer is that whenever you see the contents of the form
being shown it is when you are at SOME real record position, either an
existing one or the new record position. When none of those are available
there is nothing to display.
If nothing else there needs to be some way to distinguish between an empty
form where you can still enter a new record and an empty form where you
cannot.
