[AccessD] Fw: Access Question: Modal Form Question

Rocky,

    A work-around is available, almost like having the cake and eat it too. Following course of action is suggested.

    In the main form (say F_Normal), put a public subroutine (say P_FillModal()), incorporating all the actions that you wish to be performed after opening the pop-up modal form (say F_Modal).

    In load event of the modal form, call the above subroutine via sample syntax given below.
    Forms("F_Normal").P_FillModal

    Caution: In the procedure P_FillModal() on form F_Normal, if any statement involves reference to this form itself, avoid use of Me qualifier. Instead use the full syntax as follows
    Forms("F_Normal")

Best wishes,
A.D.Tejpal
--------------

  ----- Original Message ----- 
  From: Rocky Smolin - Beach Access Software 
  To: AccessD at databaseadvisors.com 
  Sent: Thursday, October 27, 2005 21:15
  Subject: [AccessD] Fw: Access Question: Modal Form Question


  Dear List:

  This is from a friend.  Any ideas on this?  

  MTIA,

  Rocky Smolin
  Beach Access Software
  http://www.e-z-mrp.com
  858-259-4334

  ----- Original Message ----- 
  From: "Mike Dwyer" <mike at aesadvantage.net>
  To:Sent: Wednesday, October 26, 2005 6:49 PM
  Subject: Access Question: Modal Form Question

  Ok, I know this has been discussed before so here goes again...

  1.  I have a form that must be opened as a dialog box.
  2.  This form is called from one or more VB procedures.
  3.  Before this form goes "Modal" I need to change some values on this form from my VB procedures.

  4.  While this form is "Modal", all other code must be suspended.

  My catch 22 is that I need to manipulate this Modal form to change values on it but opening this form as DIALOG causes all code to stop.
  Opening this form regularly, setting my values, and then setting the form's Modal property doesn't stop my other code from executing.

  Anybody got a solution?