EOF to gray out nextButton

[BayerMeister]

Well, I still have some little issues when deleting items from the A table. The debugger does not like the expression Forms!A.subformB.Form.RecordCount, telling that the expression contains an illegal reference to a property Form/Report.



The subform is in an invalid state for a moment, just when it's Current event gets fired.

Less of an issue is that the form sometimes tells that "The action DeleteRecord is not available at the moment" -- when deleting the last item in the B form.

[maximus]

well do you want help with these issues or u can manage.

[BayerMeister]

There are some usability issues which originate in the idea of embedding all tables in one form.

To be more specific: These tables are "Customer" which has 0 to N "Delivery_notes" assigned which have "Items" assigned.
When the user decides to write down items, he might think he can just write them down and later fill out the customer and the other information. Well, there we've got the required foreign key. The items must have a delivery_note_if (foreign key) assigned. I would have to check if these entities were created when entering items and maybe create them right away.

To achieve a usable behavior I decided to split up the form into more simpler forms. This way I can even use the built-in NavigationButtons and won't have to hassle with graying out anything.

Any other questions deserve a new thread. This subject is closed. Thank you.

[RuralGuy]

Sorry but my ISP started blocking the email alerts from this forum so I lost track of the thread. I got them to fix it and I'm back up to speed (sort of ). It looks like you guys got this covered. FYI, the RecordCount property is *not* guaranteed accurate until you have done a .MoveLast, which is why I made post #5.