InfoPath Dev

I created a Purchase Order InfoPath form which has a main connection to an Access DB (tblOrders & tblOrderDetail). There are also secondary connections used to find vendor and product information. I have a repeating table for order details. Problem #1: I used an expression box to calculate an Order total, but when I submit to the DB, it won't submit the calculated total - it sends each line item's extended cost (cost*quantity).
Problem #2: Can I have users enter an item into the repeating table if it is not on the drop down list and have it submitted to the DB as a new record in the products table?

Any help is truly appreciated - have been beating my head against this wall for a week now.......

#1 - Expression boxes are not storable values. They are only for display. If you want to store a value you must use a text box. You can create a default value formula in your text box to have the same calculation as your expression box.

#2 - InfoPath 2007 provides a drop-down control that allows users to type in values not present in the list. If you are stuck using InfoPath 2003, you can have an additional text box present, bound to the same node in your schema. Users can type into that text box if they don't find the item they are looking for in the list.

Mr. Collins:
Thanks for the suggestions. Problem #1 is solved. Problem #2 brings up another question:

If I try to add a text box bound to the same node, I get the control stores duplicate data error. How do I work around that? The original drop down box that I want to be able to edit "on the fly" is bound to a secondary data connection (therefore it is only receiving data), so should I create a new table in my database and add it to the "Main connection" and if so how do I eliminate the one to many issue that that brings?

Again, thanks for your assistance - truely appreciated.

Kammy

The message you are getting is not an error, but rather an informational message. It is quite okay to have 2 or more controls bound to the same data node. The warning is just so that you know that there is potential for a user to accidentally overwrite a value in one location in the view from another location.

In your case, both controls are in the same location... the user either selects an item from the drop-down or types in a value in the text box.