My own Cascading List Disaster.. - InfoPath Dev
in

InfoPath Dev

My own Cascading List Disaster..

Last post 07-31-2007 02:19 PM by Greg Collins. 8 replies.
Page 1 of 1 (9 items)
Sort Posts: Previous Next
  • 07-25-2007 11:53 AM

    • SSpiroFL
    • Not Ranked
      Male
    • Joined on 07-25-2007
    • Tampa, FL
    • Posts 5

    My own Cascading List Disaster..

    First of all, LOVE this site. I've learned so much.

    I've read tons of threads on cascading lists, but I'm failing miserably. I am creating a quotation form, and have many different sections that will feature cascading list boxes.

     
    First section is customer info. If I select from a drop-down box the customer's name, I want to populate the address, acct number, email, name, phone, fax, etc.

    I setup according to guidelines on here, but when I preview the form and select the customer's name, nothing happens.

    Second section is the items/quote section. I want to select a vendor, which will then allow me to select their part number in the second box, and then in the third box the description fills in automatically, as well as unit of measure and distributor cost in a field off to the side from which markup calculations will be made.

    Thus far, I am 0% successful. I don't mind posting a link to the document, but I need some serious help, and I really need to learn how to do this. If I can pull this off, then I have quite a few more forms I'd like to design to do the same. Also would like (long term) to set these up for web interface...
     

  • 07-25-2007 02:00 PM In reply to

    • SSpiroFL
    • Not Ranked
      Male
    • Joined on 07-25-2007
    • Tampa, FL
    • Posts 5

    Re: My own Cascading List Disaster..

    Just to give more info.. I've been referencing this post.

     http://www.infopathdev.com/blogs/greg/archive/2005/07/14/Create-a-Repeating-Cascading-List-from-a-Flat-Data-Source.aspx

    Where I get stuck is at the "current()/my:Year" formula section. InfoPath 07 doesn't seem to like this..? And I'm using a Access 2007 db, not a XML.

     

  • 07-25-2007 10:15 PM In reply to

    Re: My own Cascading List Disaster..

    Hi SSpiroFL,

    Sorry to hear you're having trouble. I'll ask Greg to reply.

    Patrick Halstead
    Project Manager at Qdabra
  • 07-26-2007 04:40 AM In reply to

    • SSpiroFL
    • Not Ranked
      Male
    • Joined on 07-25-2007
    • Tampa, FL
    • Posts 5

    Re: My own Cascading List Disaster..

    Patrick Halstead:

    Hi SSpiroFL,

    Sorry to hear you're having trouble. I'll ask Greg to reply.

     

    Thank you! 

  • 07-27-2007 01:07 AM In reply to

    Re: My own Cascading List Disaster..

    Greg was sick today. Hopefully, he'll be able to respond tomorrow. Thanks for your patience.
    Patrick Halstead
    Project Manager at Qdabra
  • 07-27-2007 04:47 AM In reply to

    • SSpiroFL
    • Not Ranked
      Male
    • Joined on 07-25-2007
    • Tampa, FL
    • Posts 5

    Re: My own Cascading List Disaster..

    Patrick Halstead:
    Greg was sick today. Hopefully, he'll be able to respond tomorrow. Thanks for your patience.

     

    Not a problem - Look forward to his reply. 

  • 07-27-2007 09:24 AM In reply to

    Re: My own Cascading List Disaster..

    "current()/my:Year" is based off of the specific XML example used in the article.

    You mentioned that you are using an Access database. You will need to adjust what you are reading in the article to match the schema provided in your Access data source rather than the XML I provided in my article. Also, the namespace "my" is going to change because the secondary data source for the Access database will not use the "my" namespace, but something different. You will need to make all these adjustments based off of your particular scenario, data sources, namespaces, schemas, etc.

  • 07-30-2007 04:34 AM In reply to

    • SSpiroFL
    • Not Ranked
      Male
    • Joined on 07-25-2007
    • Tampa, FL
    • Posts 5

    Re: My own Cascading List Disaster..

    Greg Collins:

    "current()/my:Year" is based off of the specific XML example used in the article.

    You mentioned that you are using an Access database. You will need to adjust what you are reading in the article to match the schema provided in your Access data source rather than the XML I provided in my article. Also, the namespace "my" is going to change because the secondary data source for the Access database will not use the "my" namespace, but something different. You will need to make all these adjustments based off of your particular scenario, data sources, namespaces, schemas, etc.

     

    Any good links to read on this syntax? 

  • 07-31-2007 02:19 PM In reply to

    Re: My own Cascading List Disaster..

    I don't have any specific links, but its just standard XPath syntax you would likely need to brush up on.
Page 1 of 1 (9 items)
Copyright © 2003-2019 Qdabra Software. All rights reserved.
View our Terms of Use.