(20080605) __
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com
---
OzMOSS.com - to unsubscribe from this list, send a message back to the
list with 'unsubscribe' as the subject.
Powered by mailenable.com
Thanks Matthew
Ishai and Nigel have tested it; it appears to not be a problem with SPD,
but WSS. Unfortunately there is no event id on my server associated with
it .It probably has to do with my installation. I'm guessing it is
either my setup of ASP.NET, or permissions on my sql. I've had to
Not sure, but maybe remove the Query element, probably not needed. Also feel
free to use single quotes instead of doubles to make the code cleaner.
Matthew Cosier
Readify | Dev Centre Lead
M: +61 401 932 250 | E: [EMAIL PROTECTED]mailto:[EMAIL PROTECTED] Blog:
This is a hunch thats all (and I never followed this email thread sorry
mate), but when a problem looks to be something odd with WSS, especially
after a restore, try and to a STSADM export and even grab Gary Lapointe's
STSADM extensions as well.
If something is indeed corrupted or simply
It's possible your ASP escapes are being taken literally in the query.
You might also variations of:
@QueryWhereEqFieldRef Name='Title' /Value
Type='Text'{0}/Value/Eq/Where/Query;
and
@'QueryWhereEqFieldRef Name=Title /Value
Type=Text{0}/Value/Eq/Where/Query';
From: [EMAIL
I had the same sort of issue, for some reason it does not like XML in @ style.
I changed from
@QueryWhereEqFieldRef Name='Title' /Value
Type='Text'{0}/Value/Eq/Where/Query;
to
QueryWhereEqFieldRef Name=\Title\ /Value
Type=\Text\{0}/Value/Eq/Where/Query;
From:
