InfoPath Dev

I'm wanting to use drop down list boxes to filter down choices in a secondary data connection but all I want to store to the main connection table is the ID of the filtered choice....  Infopath seems to require that everything be bound to a table to submit data to.  Is there any way to have a control that just display info but not save data?

 For example,  I have 3 drop down boxes "Category", "Type", Element".  If the user selects a Category, the Types are filtered and then the user selects the Type and the Elements are filtered.  Every element in the table has a corresponding ITEM ID.  All I want to save to the table that my main connection submits to is this ITEM ID however it is making me bind all three drop downs but I don't want to save that data anywhere...Just the ITEM ID.

 Is there any way to do this?

Thank You!

The dropdown must be bound since while the form is in use the field must be stored somehow to allow other fields to read the data and perform their filter.  Are you concerned with keeping your schema pristine?  You can add an additional secondary data source (XML) which can be used for these programatic fields and keep your data pure.

If you are using a database type from and submitting data to a DB then you can add nodes to your Main Node which will not be submitted to your table. Only the Data node is allowed.  So you can add additional fields to your form without having them in your table structure too.

If you are working with tables and backend data I would recommend you look at the Database Accelerator. Qdabra Database Accelerator Suite Version 2.1.2815 - Developer

This gives you much greater flexibility an dcontrol of how you can interact with your data.  You can query and submit to multiple unique tables instead of just one with the standard form.  In your example then instead of having to load the entire table you can increase performance by only returning the data needed.  So you get a list of categories and as the user selects one it queries for only the types of that category and then only the elements of the type so that you have much less data being moved back and forth and filtered through.

If you need more information or a demo let me know.

Yes, I am submitting to an Access Database and I hate to store these fields when they are unnecessary (and a big no no in the Access world).  Unfortunately I know nothing about adding nodes to my Main Node...  Is this a different option than the XML option that you also mentioned?

 Also, I have seen a lot mentioned aobut the Database Accelerator in this forum but am wondering, is it free and if so, if I develop something using it, would other users also be able to use form or would they have to have the accelerator as well?

 Thank you so much!!

When you have your form, created to submit to your Access DB the Main data source will have

Main:

       Query

       Data

 If you view the datsource task pane and then right click on main, one of the options is to add.  This is how you create new groups or fields as they are neded.

Using another XML data source is different.

 WIth Database Accelerator you would need SQL express instead of Access, which is free and performs better in a multiuser environment.

Qdabra Database Accelerator Suite Version 2.1.2815 - Developer 

Database Accelerator is a suite of webservices which allow you to interact with your database from your InfoPath forms both to query and submit to multiple tables within the same form, which cannot be done with the stock data form.  You also then can have your forms stored in a database for performance and security.  SQL Express is free and so is the developer version of DBXL.  You only need this installed on your central DB and then everyone else just uses the InfoPath form. Only connectivity is required, which is the same for a form using Access.

If you have a enterprise solution it is recomended you have a server or machine which host the DB and DBXL for all the forms to access.  Please visit http://www.qdabra.com for more information and pricing of the licensed versions.

Awesome!  I was able to add a group that includes all of my drop down boxes and they work without having to save to the table but here are blue exclamation points by them stating something about it not being able to repeat because it's not in the correct group.  Is this a big deal?  I really don't need it to repeat since it's just going to be populating the field that does need to repeat based on selections so is it okay to leave it as is?

I am attempting the same thing, however this is problematic when the multiple dropdown boxes are within a repeating section.  If you have more than one instance of the section, modifications to one section will affect the other.

I am guessing that the dropdown values that are captured need to be added to the Main datasource (on the physical database)?  This basically contradicts the original intent of the database design to be able to simply store the ID that points to the referential table that has the distinct values that correspond to the ID (and also the selected values in the dropdown).

Is there another option.  Again, the main datasource is on SQL Server.  Can you add "fake" fields in some way to a child entity in the main datasource to serve as placeholders to drive subsequent DD selections, but not record to the DB?  Can you Add a new repeating group to the Main Datasource and "link" it somehow to the database entity for which you are trying to record information?

Hi

Easy for me to drop in at the last minute but for your situation it will not cause a problem at all. 

Glad to hear you are succeeding with one of Microsoft's MOST useful tools

Cheers

Hi

If I understand you correctly you want the non-bound control to repeat.

To do this, click on 'myFields' in the data source task pane, then at the bottom add a field or group, depending on your requirements, add a group and tick the repeating tick-box or a field and tick the repeating tick-box.

That should do the trick

Cheers