InfoPath Dev

The form was created in JScript....  is that the issue?  Is there a way to convert it to VBScript without axing the entire form?

I've built an InfoPath form that is accessed via a Sharepoint site.  The user fills out the form and hits submit.  The submit button sends the data to an Access Database as well as to an Outlook Inbox via rules.  This works fine for me and one of my other coworkers.  For other users, they get the following error upon ...

I have a similar problem that would utilize whatever the solution to this is!  The reason I need the drop down box to autopopulate with the first selection in the list (rather than the blank) is that the user will not always have to select something from this drop down box (because there's only one option based on other selections in ...

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 ...

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 ...

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 ...

Well, it lists everything but there are lots of blank lines and the entries are still listed as many times as they are in the table....

Sorry, I had NOT on the brain...   I have it set at CategoryName=Category and TypeName=Type and The Expression not(.=../preceding-sibling::d:tblSAAuditItems/@Element) This filters fine except that I don't get of my results due to having some elements in the table multiple times. If I change the filter to ...

I am using the wizard though so I have 3 lines:  CategoryName is not = Category TypeName is not = Type The Expression not(.=../preceding-sibling::d:tblSAAusitItems/@Element) I'm not sure I understand what you are suggesting.  Seems the order I have them in the wizard should work but it's not.  Well, it is... but a ...

Lets see if I can make this a little clearer than mud.  I have 3 cascading drop downs.  Category>Type>Element.  If you select a category, it filters the types down to those in that category and if you select a type, it filters the elements applicable to that type.  This works like a charm all the way down to the unique ...