make field read only vb.net ? - InfoPath Dev
in

InfoPath Dev

make field read only vb.net ?

Last post 10-31-2005 02:37 PM by vt_asparagus. 2 replies.
Page 1 of 1 (3 items)
Sort Posts: Previous Next
  • 10-31-2005 12:59 PM

    • nkelkar
    • Not Ranked
    • Joined on 09-30-2005
    • Canada
    • Posts 11

    make field read only vb.net ?

    A simple option which I am unable to conclude or get an answer.

    Field(s) on the form need to be made read-only during runtime, "How do I make a field read only in managed code (I am using vb.net, based on some logic)?"

    I know there are options within infopath, by clicking on field properties and changing Display -> ReadOnly BUT BUT BUT, thats not what I want to do. The field read-only property should be controlled using runtime code.

    Searched extensively, but no answer yet. Any pointers would be appreciated.

    Thanks

    nkelkar
  • 10-31-2005 01:16 PM In reply to

    • nkelkar
    • Not Ranked
    • Joined on 09-30-2005
    • Canada
    • Posts 11

    Re: make field read only vb.net ?

    One alternate suggested by Patrick Halstead (on another group) is to have a boolean field called as say "FldReadOnly"

    On Form load (or other) use the business logic to check if the fields on the form need to be read-only or allow them to be edited. If fields need to be readonly, within your managed code you can set the field "FldReadOnly" value as True. In the conditional formatting (UI) for InfoPath, check id "FldReadOnly" is True, if True disable, else allow editing. A default value for "FldReadOnly" can be False.

    Thats the best option I have so far.

    Any comments.

    Thanks,

    nkelkar
  • 10-31-2005 02:37 PM In reply to

    Re: make field read only vb.net ?

    I assume you are referring to something like xdExtension:FldReadOnly() in your conditional formatting. If so, that is the closest thing I know of out there.
    Jason
    http://www.k2distillery.com/
Page 1 of 1 (3 items)
Copyright © 2003-2019 Qdabra Software. All rights reserved.
View our Terms of Use.