InfoPath Dev

Hello,

Sorry in advance if this is a silly question, but I've started designing forms in Infopath 2003 (SP1) for my organisation about 4 weeks ago and have had no training so am very new to all this!

The form I've been working on will not open today - I get the following error:

 Infopath cannot open a new, blank form.
The form template is not valid. 

Details:
InfoPath cannot open the following view: View 1
The following view file is not valid: view1.xsl
The .xsl file is not valid XSL.
Expression expected.

<--

The only difference today is that I am sat at a different network PC - would this matter? Would the form I am designing rely on any local data to run properly? I've subsequently gone back to the original PC and it won't work there either anymore (despite not having saved the form since the errors).

Can anyone help me? This form needs to go live in a few days' time!

Thanks in advance.

 Jo

It could be that this other PC is lacking some kind of feature, like MSXML, or MSXSL that is preventing the xml/xsl from being parsed properly. Perhaps that PC has had certain features uninstalled or disabled, or is not up-to-date with IE6 or later?

Thanks for your reply. No, the PCs have the same image on them so I don't think it's that. Could it be something to do with the supporting files that each Infopath template creates? I'm not sure where it stores these files by default - how could I find this out?

Jo

Hi jorobertson and welcome to the world of InfoPath!

It's possible that the XSN for the other computer has become corrupted. You should clear the cache by opening InfoPath, clicking "Recently Used Forms" on the left side under Form Categories, and then clicking "Remove this Form" from the right side.  That is, if you are using IP03.  The same operation should be able to be done from the welcome window on IP07, but I don't have it installed right now.  After the cache is cleared, download the XSN to the client again and try opening.

Hope this works for you!

If you are working with a XSN file, then all the supporting files are typically contained within the XSN itself. It is possible to make a connection to a secondary data source that is not contained within the XSN. This is typical of database and Web service connections, however it is also possible with XML files.

If the above were the case, then perhaps this could be a permissions issue.

Actually, according to your original post, the issue appears to be with the XSL file itself.

You could try extracting it out (an XSN is just a renamed CAB file), and test the XSL to see if there's been some corruption or it is otherwise invalid for some reason.

Thanks so much for all your help. I've fixed the problem! I did what Matt suggested about clearing the cache and it seems to have done the trick. I am soooo grateful!

 Thanks again, very much.

Jo

Glad to hear you got it working with a simple fix!