Results 1 to 4 of 4
  1. #1
    Join Date
    Nov 2003
    Posts
    18

    Unanswered: -

    -
    Last edited by TheGame7; 12-10-03 at 10:38.

  2. #2
    Join Date
    Sep 2003
    Location
    MI
    Posts
    3,713
    Yes. It depends on how you setup the child form ...

  3. #3
    Join Date
    Sep 2003
    Location
    MI
    Posts
    3,713
    I understand you perfectly. I still stand by what I said before ... It depends on how you setup the other form ... Is it bound to a table? Query? If so, populating the table (or table the query runs on) will do the trick ... If the form has unbound controls you might have to do more work to hook everything up and display the data ...

    You have to provide more details of what you're trying to do and how you've designed your forms to get a better answer.

  4. #4
    Join Date
    Nov 2003
    Location
    Riga, Latvia
    Posts
    36

    Try this out

    Getting the new form to open with the records you need can be achieved by using the DoCmd.OpenForm "where condition" argument, like this:

    DoCmd.OpenForm "frmBookings", acNormal, , "HERE GOES YOUR WHERE CONDITION", acFormEdit

    Where condition is dependent on how your data model looks like. If the records in the new form correspond to the main form, then it will look similar to

    [RefID]=[<MainForm>RefID]

    If the records in the new form correspond to the subform of the main form, it will look like

    [ID]=[<MainForm.Subform>RefID]

    RefID in both examples is the field that matches the ID (or whatever else) field on the newly opened form, and stuff in <> should of course be replaced by something like Forms!frmName, etc...
    Replies based on my configuration: Windows XP / Microsoft Office Access 2003 unless specified otherwise.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •