Changing data in secondary form - InfoPath Dev
in

InfoPath Dev

Changing data in secondary form

Last post 10-01-2005 12:40 AM by Patrick Halstead. 3 replies.
Page 1 of 1 (4 items)
Sort Posts: Previous Next
  • 09-27-2005 09:06 AM

    • Roman
    • Not Ranked
    • Joined on 09-27-2005
    • Canada
    • Posts 1

    Changing data in secondary form

    Hi all,

    I'm new to the Infopath and this group and I need your help.
    Currently I'm working on a project that involves several Infopath forms that are linked together. There is one master form, from which I create secondary forms.
    What I need is to find a way to update my secondary forms based on the changes made to the master. e.g. Form Status.
    If the Form Status field changes in the master form I want to update all secondary forms with the same value, without opening them.

    Is this possible, and if yes what needs to be done?

    Thanks,
    Roman
  • 09-28-2005 02:23 PM In reply to

    Re: Changing data in secondary form

    You will need to write some automation code to do this... and your code will have to open each form, change the value, and save again.

    For your master form to do this it will need to be set to use full trust security.

    Greg Collins [InfoPath MVP]
    InfoPath Dev
  • 09-30-2005 07:40 AM In reply to

    Re: Changing data in secondary form

    I would suggest putting the whole lot of your forms into one, where each one has a different View. This way they're all consolidated and you don't have to write "automation code". If you're worried about security and users not being able to get into the "Admin form" you could hide that View from the list and create another View that has one field on it asking you for a password. After entering the password and hitting enter you are switched to the Admin view.

    ---------------
    Matt Faus
    Matt Faus / Microsoft InfoPath MVP
    Qdabra® Software / Streamline data gathering to turn process into knowledge
  • 10-01-2005 12:40 AM In reply to

    Re: Changing data in secondary form

    I'm not sure I would do that since it creates a monster schema and subsequent XML file. Why not use Import and separate the forms? Automation code is not that hard, but Matt's suggestion is relevant for users who don't want to deal with Import or other workflow mechanisms.

    Patrick Halstead [InfoPath MVP]
    InfoPathDev
    Patrick Halstead
    Project Manager at Qdabra
Page 1 of 1 (4 items)
Copyright © 2003-2019 Qdabra Software. All rights reserved.
View our Terms of Use.