View Single Post
  #4 (permalink)  
Old June 10th, 2003, 11:46 AM
SerranoG SerranoG is offline
Friend of Wrox
Points: 4,007, Level: 26
Points: 4,007, Level: 26 Points: 4,007, Level: 26 Points: 4,007, Level: 26
Activity: 0%
Activity: 0% Activity: 0% Activity: 0%
 
Join Date: Jun 2003
Location: Lansing, Michigan, USA.
Posts: 1,151
Thanks: 2
Thanked 14 Times in 14 Posts
Send a message via ICQ to SerranoG Send a message via AIM to SerranoG
Default

Quote:
quote:Originally posted by shepston
 That is a good idea but because of layout issues, it cannot be maximized.
 Ah, then consider one of these two options.

1) FormC is a small form. Why not set its modal property and Pop-Up properties to YES. Set its border style to DIALOG. You would not hide the calling form, it would still be visible but it will be behind FormC. Because of the three latter settings I mentioned, users will not be able to click outside of FormC until they fill it out and click OK or CANCEL. In this way, FormC is a pop-up box people fill out. No need to hide the calling form.

2) If you STILL want to hide the calling form, on the button that opens FormC, set a global variable in the OnClick event. For example gstrCallerForm = "FormA" (or "FormB"). Then in FormC when it gets closed, the last item on FormC's OnClose Event will be
Code:
   If gstrCallerForm = "FormA" Then
      Forms.FormA.Visible = True
   Else
      Forms.FormB.Visible = True
   End If
Given the size and purpose of FormC, my preference would be option 1. Option 2 would leave a lot of "naked" space around FormC that I would not like. Especially if that naked space exposes the tables, queries, or whatever happens to be under both Forms A and C (or B and C).

Greg Serrano
Michigan Dept. of Environmental Quality, Air Quality Division
Reply With Quote