In an Access 97 application I am developing, I have a parent form, "Maintenance". From this form the user can open another for "Financial Scenarios".
The idea is that the user can play around with the numbers for a given product in the database to see the results of negotiating better financial terms. Upon closing this scenario form, the user can either save their changes, or revert back to the original values.
I have encountered a couple of problems, and am hoping somebody can help me. I'm certain that I am overlooking something obvious...
One problem is that the parent form was still displaying the original values prior to changes made with the scenario form unless I did a requery on the form. However now I find that the parent form goes back to the first record in the control source table, rather than staying on the record the user was working with.
The other problem is that I need to prevent the user from accidently closing the parent form prior to the child form.
My first solution was to simply make the parent form invisible while the child form was open.
Somebody else suggested that I could solve both issues by closing the parent form upon opening the child, then using DoCmd.OpenForm (to open the parent form) on closing the child, I could pass the argument to bring the parent form back to the same record ID (There is a unique ID number for each product, and a corresponding field for this on both forms). However I have been unable to figure out how to make this work.
I hope I have stated this clearly enough that perhaps somebody can help me, or point me to a sample database somewhere in which a similar action is being performed.
As I said, I just know I am missing something stupidly simple. However I have gotten my brain into a mental rut, and keep banging into a wall without achieving the results I need.
Prompt assistance would be greatly appreciated, as I have to roll out a prototype of this as soon as I can. This one item from the user's wish list is just making me nuts!
Many thanks in advance.
The idea is that the user can play around with the numbers for a given product in the database to see the results of negotiating better financial terms. Upon closing this scenario form, the user can either save their changes, or revert back to the original values.
I have encountered a couple of problems, and am hoping somebody can help me. I'm certain that I am overlooking something obvious...
One problem is that the parent form was still displaying the original values prior to changes made with the scenario form unless I did a requery on the form. However now I find that the parent form goes back to the first record in the control source table, rather than staying on the record the user was working with.
The other problem is that I need to prevent the user from accidently closing the parent form prior to the child form.
My first solution was to simply make the parent form invisible while the child form was open.
Somebody else suggested that I could solve both issues by closing the parent form upon opening the child, then using DoCmd.OpenForm (to open the parent form) on closing the child, I could pass the argument to bring the parent form back to the same record ID (There is a unique ID number for each product, and a corresponding field for this on both forms). However I have been unable to figure out how to make this work.
I hope I have stated this clearly enough that perhaps somebody can help me, or point me to a sample database somewhere in which a similar action is being performed.
As I said, I just know I am missing something stupidly simple. However I have gotten my brain into a mental rut, and keep banging into a wall without achieving the results I need.
Prompt assistance would be greatly appreciated, as I have to roll out a prototype of this as soon as I can. This one item from the user's wish list is just making me nuts!
Many thanks in advance.
