Event procedures Primary Form

ru1 · February 28th, 2005, 02:13 PM

Hi everyone. I have this STRONG RUNNING database where on a primary form I have totals that come from summing up the information on a subform. For instance, If a judge has 12 cases on his docket with a total of say 30 plaintiffs and 12 defendents, I show the respective totals. But, if I add a plaintiff to one of the cases, the numbers on the primary form does not refresh.

In moving from a subform to a primary form, which event procedure do I need to use to refresh my totals. Better yet, is there a way on the subform to refresh the totals on the primary form after the number has been changed on the subform?

Any help would be highly appreciated.

Thanks,

Ru1

dartcoach · February 28th, 2005, 02:30 PM

On your subform, when you change or add, try using the "after update" event procedure.
whatever field needs to be updated,

Mainform.field.requery

Hope it helps

dartcoach

ru1 · February 28th, 2005, 02:51 PM

Thanks for the suggestion, but that sill doesn't help. I need to run the code that builds the totals. Any other thoughts?

RU1

dartcoach · February 28th, 2005, 02:54 PM

Where is the code? Is it in a module?

dartcoach

ru1 · February 28th, 2005, 02:59 PM

Yes. It is in a module.

dartcoach · February 28th, 2005, 03:01 PM

can you call the module from the after update procedure?

dartcoach

ru1 · February 28th, 2005, 03:05 PM

No. It is in the current event procedure of the primary form.

rjweers · March 4th, 2005, 10:22 AM

Well actually, yes you can call the Form_Current of the main form. However, you need to change from "Private Sub Form_Current" to "Public Sub Form_Current". Beware, that can make things very confusing, especially if you try to do that with more than one form...

A better way to do this is to create a "Public Sub UpdateTotals" procedure in the main form, or any module (which is what dartcoach was really asking), and have the Form_Current of your main form call that. Other modules and forms can call it too. If you create the UpdateTotals in something other than your main form the procedure won't have a context for the fields of your main form which means you'll have to use specific reference to the form to update the fields (e.g. Forms("main_formname").field_name). So the best bet is to have that procedure in your main form.

Also, watch out for that Current event, especially in your child forms! It runs for so many different reasons... often multiple times.

Randall J Weers
Membership Vice President
Pacific NorthWest Access Developers Group
http://www.pnwadg.org

ru1 · March 7th, 2005, 03:58 PM

Quote:

quote:Originally posted by rjweers
Well actually, yes you can call the Form_Current of the main form. However, you need to change from "Private Sub Form_Current" to "Public Sub Form_Current". Beware, that can make things very confusing, especially if you try to do that with more than one form...

A better way to do this is to create a "Public Sub UpdateTotals" procedure in the main form, or any module (which is what dartcoach was really asking), and have the Form_Current of your main form call that. Other modules and forms can call it too. If you create the UpdateTotals in something other than your main form the procedure won't have a context for the fields of your main form which means you'll have to use specific reference to the form to update the fields (e.g. Forms("main_formname").field_name). So the best bet is to have that procedure in your main form.

Also, watch out for that Current event, especially in your child forms! It runs for so many different reasons... often multiple times.

Randall J Weers
Membership Vice President
Pacific NorthWest Access Developers Group
http://www.pnwadg.org