I think it's okay to post it here, and @GPGeorge should be able to pick it up from there.Hi everyone,
Now I have Access 2019 I was able to open the Northwind 2 DB (Developer Edition 2.3)
If one finds what they might think is a bug, are they meant to report it at all?, and if so where please?
Explain it here and, if it's not one we already know about, we can add it to the To Do list forHi everyone,
Now I have Access 2019 I was able to open the Northwind 2 DB (Developer Edition 2.3)
If one finds what they might think is a bug, are they meant to report it at all?, and if so where please?
The application is driven from the ribbon. So, if there is an entry point on the ribbon, that would be the way to do it. I'll have to refresh myself, though, as it's been many months since launch.OK, thank you.
First a question. Is one meant to go into form frmEmployeeTitles directly, or are they expected to get there via another route?
Thank you. One of the dangers of testing is that you get used to doing the same things the same way and don't stumble on problems on on paths. I'll make sure it gets on the list to be addressedI do not appear to have that icon?
View attachment 113814
Edit: OK, found that with a right click, but the behaviour is the same.
When go go into the form it automatically adds an empty record at the top, whilst you are on the bottom record about to enter a new value.
Decide you do not want to add one anyway and are unable to close the form without an error message.
I just found it by going to the form from the navigation list.
View attachment 113815
Private Sub Form_BeforeUpdate(Cancel As Integer)
If Nz(Me.Title, "") = "" Then
Me.Undo
End If
End Sub
It is more to do with a ZLS in that initial record. You've added a number of records in your screenshot, and none of them have the ZLS any longer.OK, I think it might be just due to no validation on an empty record, and as the table is
View attachment 113827
then that record appears at the top and the new record is at the bottom.
That appears to be my issue.
I added
and that appears to correct it.Code:Private Sub Form_BeforeUpdate(Cancel As Integer) If Nz(Me.Title, "") = "" Then Me.Undo End If End Sub
I know you would expect a developer to add their own validation, but I was just looking at a few forms, and found this issue doing that.
So as you say, not a bug.