Hi,
This is correct. I think this is happening because in LRE 3 we alloweither %1 or %01 to work as a replacement for parameter 1. As Lindsay says,you can use %% to escape the % sign if you don’t want the percent sign to be interpreted.
Greg Petti
From: eLink Discussion:Livelink LiveReports Discussion[mailto:livereportsdiscussion@elinkkc.opentext.com] Sent: November 19, 2008 7:33 AMTo: eLink RecipientSubject: RE error messages since install of livelink extentions 3.0
RE error messages since install of livelink extentions 3.0
Posted by ldavies (Davies, Lindsay) on 11/19/2008 07:32 AM
In reply to: error messages since install of livelink extentions 3.0
Posted by genzymeuser20 (Vermeulen, Katia) on 11/19/2008 06:04 AM
Message from Lindsay Davies <ldavies@opentext.com> via eLink
The % character is how variables are referenced.
Try doubling up the % characters to allow them to be treated as literals.
So, %%01 would end up being %01 in a string.
From: eLink Discussion: Livelink LiveReports Discussion [mailto:livereportsdiscussion@elinkkc.opentext.com] Sent: 19 November 2008 11:06To: eLink RecipientSubject: error messages since install of livelink extentions 3.0
error messages since install of livelink extentions 3.0
Since Livelink extensions 3.0 is installed on our system we receive error messages in our existing livereports. We are using stings as user iput type. This was no problem until the instal of Livelink extensions 3.0. But now if a user gives an input like %01, %02, %03 meaning search everything ending on 01, 02 or 03 this input will be replaced by the first, secend or third iput field whitch causes an error message if this input is an other type. I hope someone can help me to find a solution for this.
[To reply to this thread, use your normal E-mail reply function.]
Topic:
Discussion:
Livelink LiveReports Discussion
Livelink Server:
knowledge-wlweb01
To Unsubscribe from this Discussion, send an e-mail to unsubscribe.livereportsdiscussion@elinkkc.opentext.com.