InfoPath Dev

Jim,    I have removed the form viewer and everything works great.  If I do want to use the form viewer, how would I fix this issue?  I want to make sure that if the person has Infopath (and all computers do with sp2) that the form viewer does not open.   Jeff

Hi All,  We have rolled out a new form created in Infopath2003.  For standard users with Office2003 it works fine.  However some users are testing office 2007 (except outlook - this is still 2003) and when they click on submit the email box dosent appear but there are no error messages, it looks like the form has been sent but it ...

No this happens on anything, and no I am not using VS.  I actually thought that might have been the problem so I uninstalled it.  Do you have to you VS if you intended on combing your infopath form with Sharepoint?  I was hoping to use  java. 

For me, this same error does happen on every form (existing and new).  In reading the blog mentioned above, I read that this will only work on a SharePoint 2007 server install, is that correct?  I am working on my local machine that has all but SharePoint 2007 installed, is that really required for this to work?

Does this happen on any form you try and link code to or only one in particular? Are you using Visual Studio?

To my knowledge the New Record button is like opening a new form. So yes you would want to make your own reset button or add rules to the submit to clear the fields you want after submitting the current data. Another option is to seed your database query with a value that will return nothing, maybe 0 or something and run the query again which ...

Ok trying to follow this... Data in your form is persistent, views are just ways of representing the information with controls. You should have one repeating group of fields with information. In View A you would have a repeating table bound to the repeating group, in View B you would have a repeating section with controls bound to the same ...

The key steps are to add the web service path to your list of excluded paths, so that SharePoint doesn't intercept it. I think we have this documented in the installation notes for the DBXL Web Service Suite. More soon,  ...  oops! on MOSS 2007, you don't have to exclude any managed paths. So, ignore that previous comment. ...

Thanks, Got it figured out. Now, I'm trying to enable your component on our SharePoint 2007 server.  Do you have step by step instructions somewhere to do so?