InfoPath Dev

I'm looking for some guidance because what I'm experiencing can't possibly correct. I have created data connections, converted them to site collection relative and then uploaded those to Central Admininstration - which seems like an extra step but I digress Whenever I try to create a new form and add one of the dataconnections ...

My problem is as follows:  We have a custom content type called eForm that inherits from Form. I have a browser based InfoPath form with code behind that needs to be deployed as a feature AND needs to inherit from eForm The content type deploys properly and inherits as expected when I try to launch the form in the browser the ...

I have created a simple test form and packaged it up as a feature and deployed it to the SharePoint farm.  Everything works as expected.  When I attempt to activate the feature in a site collection I get the following message: There has been a critical error while processing the form. Interestingly the form template is copied ...

I have published a browser based Infopath form to a form library and enabled versioning on the library.  The form functions as expected however when I look at the version history (.../_layouts/Versions.aspx) and click the links to previous versions they only open in the InfoPath client.  Is this by design or am I missing ...

I think this is a moot point actually because if I simply upload the xsn to a form library I don't think I'll be able to get it to open in a browser.

Ok - I just tested it in our evaluation version and I am not seeing the result I had hoped for.  Is it possible to push the XSN to a form library so the XSN itself is an item in the library?  So users can open the template by clicking on the item and not using the New menu?  Does that make sense?

Thank you for the quick response.  I believe you have answered my question.  If I'm reading you correctly once DBXL owns the xsn, I can use the tool in order to push that xsn to a form library. The goal is to have libraries containing the actual XSN files so users can see them, open them, fill them out and submit them somewhere ...

I think I found the answer elsewhere in the forums but if someone can verify for me I would appreciate it. I can use the DAT to upload the XSN and do any required mapping to SQL and then save the XSN from the DAT and put in in a SP library - as long as I don't go through the InfoPath publishing process. Is that correct?  

We have approximately 100 forms that will be migrated to InfoPath.  Some will require submission of the data to SQL server but most won't.  My intention is to logically group the xsn files into different libraries where the users will fill them out.  These templates will be primarily open access.  Once they are submitted, ...