locked
Looking better solution to handle write conflicts Overlapping Windows app RRS feed

  • Question

  • There are almost 100 forms/subforms in this application. This app does quite a lot. To avoid write conflicts I've pretty much created a controller that I use to open most forms in the application. It doesn't control much, it really just closes all other forms in the user's application before opening the new Form. The exceptions are some dialog forms.

    I've restricted opening multiple windows because write conflicts by a single user. I've learned that users can't deal with saving a record on 1 window before going to another, AND they will leave a billion forms open if you let them. This is fine, except when they get write conflicts, its like trying to teach Chinese to a rock explaining how they can work around it by just saving their work and closing windows. =). I would like to give the users the ability to use Overlapping Windows so they can have the option to compare info in multiple forms quickly. Currently I have the system locked to only Tabbed Documents without showing Tabs. 1 Form open at any given time.

    I'm thinking of using the Active/Deactive events of a form to just set Me.Dirty = False forcing the record to save when the user goes on to another window. Would this solve my dilemma? Can anyone offer me some guidance?

    Thanks again!
    Monday, February 15, 2016 9:37 PM

Answers

  • I'm thinking of using the Active/Deactive events of a form to just set Me.Dirty = False forcing the record to save when the user goes on to another window. Would this solve my dilemma? Can anyone offer me some guidance?

    Hi HTHP,

    I don't think there is a general recipe to handle these things.

    In my applications I have about the same situation. A lot of form-handling can be "controlled" by a good use of Dialog forms.

    Because I can "walk" from one form to an other using the existing relations bidirectional, it is possible that an open form a second time is called. Access will bring that form to the foreground. In the command to open a form I therefore will first close the form with the same name, and then open the form again. It makes the form more dynamical.

    To even make it more dynamical, changed data is saved on the exit of a control. So whenever you go to a new form, data is already saved.

    But I think there are more scenarios.

    Imb.

    Monday, February 15, 2016 10:42 PM