John Clark
John.Clark at niagaracounty.com
Mon Jan 11 11:17:43 CST 2010
*** In line John W Clark John.Clark at niagaracounty.com ( http://www.niagaracounty.com/ ) >>> jwcolby <jwcolby at colbyconsulting.com> 1/8/2010 4:55 PM >>> John, You didn't really specify how the two forms inter-operate. does the calling form close and reopen? If so why? If it doesn't close, then it should still be at that record when you are done. *** Yes, the calling form does close, when the report is opened. I only did this for aesthetics...it looks "cleaner" doing it this way. But, you are correct and maybe I just need to leave it open. Likewise, when you say "data entry form" are you saying a form that opens on the new record to allow you to enter a new record (data entry mode)? Or just "generically" a form that you use to enter data on. *** the latter choice...just a general form. It is trivial to pass information to an opening form. Pass in the PKID of the record that you are coming from. Then when control returns to the calling form, just seek to that record. In my framework, I often pass in the PK of the record that the OPENING form should seek to. When the form opens, it gets that PKID, then goes to the record requested. *** Hmmm...I think I like this idea. It might also play into some other ideas I have as well. Usually if I want a new form to do something but to get back to the same record in the calling form, I just leave the calling form open and open the new form modal. When I close the new form I am back where I started.