S_Records[@@request$i,12]
<@VAR SCOPE="request" NAME="MLS_Records[<@CALC EXPR='<@VAR
SCOPE="request"
NAME="i">
- 1'>,12]">
<@VAR SCOPE="request" NAME="MLS_Records[<@VAR SCOPE='request'
NAME='
ou the syntax checker?
2. Can you click open the advanced button on the IF action and post
the actual code that Witango is seeing
--Bill
-- Original Message ---
From: David Green <[EMAIL PROTECTED]>
To: witango-talk@witango.com
Sent: Mon, 12 Feb 2007 13:41:58 -0500
Subject: Re:
Johansen <[EMAIL PROTECTED]>
To: witango-talk@witango.com
Sent: Mon, 12 Feb 2007 12:56:03 -0800
Subject: Re: Witango-Talk: Upgrading from Witango 5.0 to Witango 5.5 - Syntax
Errors
> interesting so, the data structure says char(#) but it seems to be
> stored as varchar. so there is no
ed button on the IF action and
post the actual code that Witango is seeing
--
Bill
------ Original Message ---
From: David Green <[EMAIL PROTECTED]>
To: witango-talk@witango.com
Sent: Mon, 12 Feb 2007 13:41:58 -0500
Subject: Re: Witango-Talk: Upgrading from Witango 5.0 to Witan
quest" NAME="MLS_Records[<@CALC EXPR='<@VAR
SCOPE="request"
NAME="i">
- 1'>,12]">
<@VAR SCOPE="request" NAME="MLS_Records[<@VAR SCOPE='request'
NAME='i'>,12]">
--
Bill
-- Or
x checker?
2. Can you click open the advanced button on the IF action and post
the actual code that Witango is seeing
--
Bill
-- Original Message -------
From: David Green <[EMAIL PROTECTED]>
To: witango-talk@witango.com
Sent: Mon, 12 Feb 2007 13:41:58 -0500
Subject: Re: Witango-Talk
:06:02 -0500
Subject: Re: Witango-Talk: Upgrading from Witango 5.0 to Witango 5.5 - Syntax
Errors
> Yes, I opened the IF Action in Advanced mode and this is what it shows:
>
> ('<@VAR NAME="MLS_Records[<@CALC EXPR="@@request$i - 1">,12]"
> SCOPE=&quo
- Original Message ---
From: David Green <[EMAIL PROTECTED]>
To: witango-talk@witango.com
Sent: Mon, 12 Feb 2007 13:41:58 -0500
Subject: Re: Witango-Talk: Upgrading from Witango 5.0 to Witango 5.5 - Syntax
Errors
Yep, sure did. Same error.
Thanks,
David Green
[EMAIL PROTECTE
12 Feb 2007 13:41:58 -0500
Subject: Re: Witango-Talk: Upgrading from Witango 5.0 to Witango 5.5 - Syntax
Errors
> Yep, sure did. Same error.
>
> Thanks,
>
> David Green
> [EMAIL PROTECTED]
> Web Services
> Systems Insight, Inc.
> http://www.systemsinsight.com/
>
>
007 13:41:58 -0500
Subject: Re: Witango-Talk: Upgrading from Witango 5.0 to Witango 5.5 - Syntax
Errors
> Yep, sure did. Same error.
>
> Thanks,
>
> David Green
> [EMAIL PROTECTED]
> Web Services
> Systems Insight, Inc.
> http://www.systemsinsight.com/
>
> Will
t' NAME='i'>,12]">
--
Bill
-- Original Message -------
From: David Green <[EMAIL PROTECTED]>
To: witango-talk@witango.com
Sent: Mon, 12 Feb 2007 13:23:19 -0500
Subject: Re: Witango-Talk: Upgrading from Witango 5.0 to Witango 5.5 - Syntax
Errors
Hi Guys,
uot;i">
- 1'>,12]">
<@VAR SCOPE="request" NAME="MLS_Records[<@VAR SCOPE='request' NAME='i'>,12]">
--
Bill
-- Original Message -------
From: David Green <[EMAIL PROTECTED]>
To: witango-talk@witango.com
l use of the <@calc> tag?
<@calc expr="">
Shane Pearlman
831.345.7033
S&P, Inc.
-Original Message-
From: David Green [mailto:[EMAIL PROTECTED]
Sent: Monday, February 12, 2007 10:23 AM
To: witango-talk@witango.com
Subject: Re: Witango-Talk: Upgrading
TED]
Sent: Monday, February 12, 2007 10:23 AM
To: witango-talk@witango.com
Subject: Re: Witango-Talk: Upgrading from Witango 5.0 to Witango 5.5 -
Syntax Errors
Hi Guys,
I work with Adam and I'm trying to help him with the upgrade. I wanted
to give a little more info since the last email
Hi Guys,
I work with Adam and I'm trying to help him with the upgrade. I wanted
to give a little more info since the last email from support. We're
upgrading from Server 5.0 to 5.5 because of the database upgrade from
Pervasive.SQL 2000 to 9.5. For some reason, we cannot get ODBC to work
i
Adam,
This issue is probably due to one of the array elements of the
variables containing a single quote. You can fix this by using an
encoding on the variables.
e.g.
('<@VAR request$MLS_Records[@@request$i,12] ENCODING="HTML">'!='<@VAR
request$MLS_Records[@@request$i,11] ENCODING="HTML">
Well, we def hit a bug, the moment we went to 020, but we didn't have
time to track it all the way down. We found a workaround, and stopped
there. We don't know if the bug was specific to using the bean, but
it seemed it may have had to do with parsing quotes and such, maybe I
will spend th
Actually Robert, I had installed 5.5.020 but once I couldn't seem to get around
this issue I uninstall the server and re-installed 5.5.009. It DID correct the
specific issue that I was working on, but another similar issue dealing with
"Closing bracket missing at end of statement" showed up in
We are tracking a bug, that appeared in 5.5.020. Did you upgrade to
5.5.020, or 009? I am guessing, 020. I bet, you don't have the issue
with 009. I would like to know if you check.
--
Robert Garcia
President - BigHead Technology
VP Application Development - eventpix.com
13653 West Park Dr
M
We use the shorthand @@ pretty much everywhere unless we need to
specify encoding or formatting. We use <@var> a lot when generating
files - as was pointed out, sometimes you need the space on the front
of the @@ to get through the parser, but then you don't want that
space char in the file
e formal
tag.
--
Bill
-- Original Message ---
From: "Shane Pearlman" <[EMAIL PROTECTED]>
To:
Sent: Thu, 8 Feb 2007 10:54:40 -0800
Subject: RE: Witango-Talk: Upgrading from Witango 5.0 to Witango 5.5 - Syntax
Errors
> We have used @@ for years with no issues that we are awa
33
S&P, Inc.
-Original Message-
From: David Green [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 08, 2007 10:31 AM
To: witango-talk@witango.com
Subject: Re: Witango-Talk: Upgrading from Witango 5.0 to Witango 5.5 -
Syntax Errors
When exactly were we as developers told not to use the @@ shorthand?
Shane Pearlman
831.345.7033
S&P, Inc.
-Original Message-
From: David Green [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 08, 2007 10:31 AM
To: witango-talk@witango.com
Subject: Re: Witango-Talk: Upgrading from Witango 5.0 to Witango 5.5 -
Syntax Errors
When exactly were w
sday, February 08, 2007 10:31 AM
To: witango-talk@witango.com
Subject: Re: Witango-Talk: Upgrading from Witango 5.0 to Witango 5.5 -
Syntax Errors
When exactly were we as developers told not to use the @@ shorthand? I
missed that update and have been using it for the past 8 years. I just
checked with
for what it's worth i have always used @@ religiously (only using
<@var> in occaisions when i needed formatting or something) and have
had no problems (:
On 2/8/07, David Green <[EMAIL PROTECTED]> wrote:
When exactly were we as developers told not to use the @@ shorthand? I
missed that update a
When exactly were we as developers told not to use the @@ shorthand? I
missed that update and have been using it for the past 8 years. I just
checked with the 5.5 Programmer's Guide and it still gives examples
using that shorthand.
Just curious...
David Green
[EMAIL PROTECTED]
Web Services
Due to unpredictable behavior related to the interpretation of the @@
notation in Tango, we stopped using it a long time ago. I can't comment on
5.0 vs 5.5. support, because it's something that I started getting away from
back on Tango 2000
/John
On 2/7/07, Jason Pamental <[EMAIL PROTECTED]> wr
Adam,
I have no comments for or against the ( instead of [ trick - but if
it works that certainly helps, doesn't it? I would guess it has more
to do with the code shorthand not being handled properly though - and
could also be handled by a search and replace. I always write things
out a b
Thanks for the info. Jason. I've actually figured out a work-around, but it's
not one that I feel comfortable implementing.
The issue seems to occur in IF actions (not metatags), I've pasted examples
below:
Non-working example in 5.5 - working in 5.0:
@@request$exampleArray[@@request$rowCounte
Adam,
The only major 'gotcha' I encountered was making sure that all places
where I used 'encoding=multilinehtml' were change to
'encoding=multiline'. Otherwise I don't think I had any problems.
Things to look at though would also be customizations you may have
made to the witango.ini fil
Hello everyone,
We're in the process of upgrading our Witango Server from 5 to 5.5 and we've
encountered an odd issue. Applications that work properly in the 5 environment
are throwing Syntax errors. Specifically, it deals with 'Missing closing
brackets' and 'Missing quote at the end of the s
31 matches
Mail list logo
