Infopath 2003 - floating attribute error - InfoPath Dev
in

InfoPath Dev

Infopath 2003 - floating attribute error

Last post 12-12-2007 05:09 PM by abcolson. 2 replies.
Page 1 of 1 (3 items)
Sort Posts: Previous Next
  • 04-05-2007 06:35 AM

    Infopath 2003 - floating attribute error

    I just moved my managed code forms (IP 2003 SP2, VSTO2005) to a new dev box. Now all my forms get this error as I start them in VS to test:

    InfoPath cannot open the selected form because of an error in the form's code.
    A floating attribute may not be passed as the context node for an XSLT transform or an XPath query

    The error happens before the managed code ever kicks in as far as I can tell.

    The only thing different about this box (that seems relevant?) is that this machine also has VS2003 installed (but no VSTO2003)

    Thanks,

    oberonop

  • 05-02-2007 08:32 AM In reply to

    Re: Infopath 2003 - floating attribute error

    Hi oberonop,

    Sorry for the late reply - did you ever get this working? I would first do a windiff to make sure that there was no corruption in the transfer.  After this I would check to see if the form is trying to open with .NET 1.1.  There is an infopath.exe.config file that resides in the same directory as infopath.exe, and you will have to delete this.

    Let us know if you need any more help!

    Matt Faus / Microsoft InfoPath MVP
    Qdabra® Software / Streamline data gathering to turn process into knowledge
  • 12-12-2007 05:09 PM In reply to

    • abcolson
    • Not Ranked
      Male
    • Joined on 12-12-2007
    • San Diego
    • Posts 20

    Re: Infopath 2003 - floating attribute error

    Hi Matt & oberonop,

    It would seem that I have a similar issue (see my post at http://www.infopathdev.com/forums/p/6880/25080.aspx#25080).  Essentially I have an InfoPath 2003 managed code form (VS 2003 .Net 1.1).  Recently the .Net Framework 2.0 and .Net Framework 3.0 upgrades were installed on my system by our IT and that appears to be when the fun started.  I have seen posts saying that we get this error when both InfoPath 2003 and 2007 are simultaneously installed on the system but I only have InfoPath 2003 installed. 

    I am wondering if anyone knows if the "bad part" of InfoPath 2007 (which causes the problems with an InfoPath 2003 installation) is actually part of the .Net Framework 2.0/3.0 upgrades?  If so, this would explain the sudden and odd behavior but I haven't seen any explicit statements to this saying they are incompatible with InfoPath 2003 managed code templates.

    Thanks
    Tony

Page 1 of 1 (3 items)
Copyright © 2003-2019 Qdabra Software. All rights reserved.
View our Terms of Use.