What expression?

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

rivsys - 29 Mar 2005 06:27 GMT

Now that my application is in pilot, the client has requested certain small
changes here and there. Occasionally, when changing an Infopath form I get
what has to be the most stupid and useless error message ever conceived:

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

<--"

This generally occurs in a form that shows no binding issues, and in many
cases only has a few additional data elements added first to the database and
then to the primary data connection.

Does anyone have a repeatable method of debugging a form throwing this
error? Are there any telltale signs that can be divined from the .xsl file,
or do I just remove controls until I finally get the form to fix itself?

Reply to this Message

rivsys - 29 Mar 2005 06:45 GMT

Update!

Infopath successfully corrupted a completely innocent combo-box. No changes
to it's data source, no changes to its conditional formatting, no changes to
it's code. Nothing!

Buggy? You be the judge. Why am I so ascerbic and belecose? Maybe because
its 1:00 AM, my client needs this stuff in the morning and I'm screwing
around with stupid Infopath application errors that should have been fixed in
a service pack a year ago.

> Now that my application is in pilot, the client has requested certain small
> changes here and there. Occasionally, when changing an Infopath form I get
[quoted text clipped - 14 lines]
> error? Are there any telltale signs that can be divined from the .xsl file,
> or do I just remove controls until I finally get the form to fix itself?

Reply to this Message

Brian Teutsch [MSFT] - 29 Mar 2005 06:54 GMT

Yes, it is a bug. Sorry you ran into it, it's definitely something that we
hope to fix in a future release. It occurs with certain dropdown list boxes
that have conditional formatting and which get their values from a Secondary
Data Source or the form's data source.

Brian

> Update!
>
[quoted text clipped - 32 lines]
>> file,
>> or do I just remove controls until I finally get the form to fix itself?

Reply to this Message

knelsen - 30 Mar 2005 21:41 GMT

FYI - The values for my drop-down list boxes were entered manually, not from
a data source, and I still got this error. Glad to know it wasn't just me!

> Yes, it is a bug. Sorry you ran into it, it's definitely something that we
> hope to fix in a future release. It occurs with certain dropdown list boxes
[quoted text clipped - 39 lines]
> >> file,
> >> or do I just remove controls until I finally get the form to fix itself?

Reply to this Message

Rate this thread: