InfoPath Dev

Hi,

I ve designed a form in infopath 2007 and also write few chunks of VB.net code. Now when I go to Tools -> Form Options - > Programming, it shows me this message:

Script and deprecated object models are not supported in browser-enabled form templates

The form is browser enabled but cannot be viewed on browser.

 Please also suggest me solution for this: "Infopath can not create new, blank form".

Urgent help is needed.

Cheers.

Does the error not make sense?  You have to use managed code in browser forms - no script. 

You can't create a new form from a template that doesn't work.

It sounds to me like your form was set to use the InfoPath 2003 object model for your code. You'll need to change your form to use the 2007 InfoPath object model, and then port your code. First, make a copy of your code. Then, under Tools / Form Options / Programming, you can remove the code using the Remove Code button. Set the form to use either C# or VB and then rewrite your code for the 2007 OM.

Thanks for the replies. The code was basically communicating the with the Active Directory & calling a web service.

I ve removed the code & now using the built-in methods of calling web services, which is working ok now.

On the other note, I need to ask about the workflows. How can we change the link sent through email to the approvers.

 Regards,

As far as sending a link via email to approvers:

I create custom workflows in SharePoint Designer to accomplish this. I put the important information from the form in an email template in created in the custom workflow, that I want the approvers to see, and then add [%Name:Encoded Absolute URL%] at the bottom for a link to the complete form.

For a browser form, you have to embed the Encoded Absolute URL within a long string (before and after) so that you make up the entire Forms Services URL.  It's easy to do, though.  Just open a browser form, copy the URL, and replace the Location attribute with your current item's Encoded Absolute URL (just the URL portion - nothing else).  You can do this by building a dynamic string, storing it to a variable, and then referencing that variable anywhere in your workflow that needs to point to the form in browser mode.