Search results

Yes.

I want to have a single form for creating/editing the main record and its relationhips to other records, so that's the opposite of your approach. I am nonetheless interested in a presentation of how your solution works.

@Mark_ The answer to all of your questions is no. The intended purpose of my application is to store and manage the data that is generated as part of the Systems Engineering process of various projects. That is, requirements, product architecture, validation tests, etc. It is an internal app...

Hello, I am still watching this thread, I just had other priorities at work the last few days. @Albert D. Kallal, I understand that after your latest edits you are suggesting to try the second solution listed in my original post, with DAO recordsets since you say that ADO ones cannot be used...

@Gasman A user who knows nothing about Access or databases would expect it to work for the whole form just like it works for an entire Excel spreadsheet, so yes that's what I want to find an alternative to.

Thank you very much for your replies. To clarify, what I'm trying to do is replicate the standard behavior of most programs outside of Access, that have a dialog to edit an item and its children items, and the changes made in that dialog are only saved when the user clicks the OK / Save button...

Hello everyone, I am weighing my options to make a "New record" or "Edit record" single-record pop-up form including a subform for related records, that would prompt the user to save or discard the changes. As you most certainly know, the problem here lies with the subform, since on a bound...