I have an application I created in Access that is very different than I have done in the past. You are accessing the same data from several different beginning spots with drilldowns. I discovered that I needed to save the record before the drilldown, because otherwise you are editing the same record in two different places, which is obviously not a good thing.
However, I am wondering how others handle this kind of complex setup where there are multiple paths to get to the same place. I work for a General Contractor, so as an example, you might start from the client screen, and drilldown from one of the child projects into the form where you are seeing the project as parent with all the subcontractors assigned to the job as children. Then you might want to see all of the projects the subcontractor is associated with, so you drilldown to the form where the subcontractor is parent and projects are the children. You might get interested in one of the projects on that screen and drilldown into the projects/subcontractor form where the new project is parent.
What I ended up doing is making all the forms modal, but that becomes cumbersome, because maybe in the midst of this, something comes up and I need to go to the employee form.
How can I do this in a way that makes sense without having any issues with data integrity? I am considering hiding the form that was drilled down from and them displaying it when you close the next form, as I have done in other applications, but in this one, the drilldown could go so deep that I would have to have a way to track the drilldowns in from start to finish. One thing I would also want is the ability to just close the whole chain out at any point so I don't have to step through each step in the chain sequentially. The other complication of this is that you may have multiple chains going in different directions, i.e., starting down the path of two or three different projects. It has the potential to get really messy. Also, I am reusing forms. Will that cause me any issues if I am editing in a form at one place on the chain and then use it again later in the chain in a different parent form?
I worked with an application a few years back that did all of this with drilldowns. I wish I could see it again now to play with it and see how they handle different things.
I would love to hear how others have handled this type of application and any additional insights you might have.
Thanks so much for any input you can give me!