Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

retrieval arguments in computed fields

3 posts in DataWindow .NET Last posting was on 2004-08-11 22:22:32.0Z
<Pat Madigan> Posted on 2004-08-11 20:25:08.0Z
From: <Pat Madigan>
Newsgroups: sybase.public.datawindow.net
Subject: retrieval arguments in computed fields
Lines: 16
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1437
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
NNTP-Posting-Host: mail.gscutah.com
X-Original-NNTP-Posting-Host: mail.gscutah.com
Message-ID: <411a80a4$1@forums-1-dub>
Date: 11 Aug 2004 13:25:08 -0700
X-Trace: forums-1-dub 1092255908 208.11.90.3 (11 Aug 2004 13:25:08 -0700)
X-Original-Trace: 11 Aug 2004 13:25:08 -0700, mail.gscutah.com
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.datawindow.net:103
Article PK: 124540

When I try to use a retrieval argument in a computed field... even if the
only thing IN that expression is the retrieval argument... I hit the verify
button and get an "Expression is not valid" error. This is the case for new
retrieval arguments, as well as existing ones (when I imported a datawindow
from my powerbuilder application).

Has anyone else seen this? That's the only glitch I've seen so far. I can't
believe how easy it was to throw a datawindow onto a WinForm, at least for a
report.

(My apologies for not taking part in the beta, where I could have caught
this sooner. I was on another assignment... no Powerbuilder.)

Pat


Jim O'Neil [Sybase] Posted on 2004-08-11 22:05:48.0Z
From: "Jim O'Neil [Sybase]" <joneil_at_sybase_dot_com>
Newsgroups: sybase.public.datawindow.net
Subject: Re: retrieval arguments in computed fields
Message-ID: <v75lh0potd3vt0jpt9qvq9ak8th492n7cp@4ax.com>
References: <411a80a4$1@forums-1-dub>
X-Newsreader: Forte Agent 2.0/32.652
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: joneilw2k.sybase.com
X-Original-NNTP-Posting-Host: joneilw2k.sybase.com
Date: 11 Aug 2004 15:05:48 -0700
X-Trace: forums-1-dub 1092261948 10.18.63.187 (11 Aug 2004 15:05:48 -0700)
X-Original-Trace: 11 Aug 2004 15:05:48 -0700, joneilw2k.sybase.com
Lines: 27
X-Authenticated-User: teamsybase
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.datawindow.net:106
Article PK: 124542

Yup, I see it to, but only in DataWindow Designer and not in
PowerBuilder 10, which is rather odd since the code is very nearly the
same.

I see we disabled "Edit Source" in DataWindow Designer as well, but I
was able to export, change the source, and import and the expression
is working fine, it just doesn't pass validation in the painter. I'll
log this as a bug.

On 11 Aug 2004 13:25:08 -0700, <Pat Madigan> wrote:

>When I try to use a retrieval argument in a computed field... even if the
>only thing IN that expression is the retrieval argument... I hit the verify
>button and get an "Expression is not valid" error. This is the case for new
>retrieval arguments, as well as existing ones (when I imported a datawindow
>from my powerbuilder application).
>
>Has anyone else seen this? That's the only glitch I've seen so far. I can't
>believe how easy it was to throw a datawindow onto a WinForm, at least for a
>report.
>
>(My apologies for not taking part in the beta, where I could have caught
>this sooner. I was on another assignment... no Powerbuilder.)
>
>Pat
>


<Pat Madigan> Posted on 2004-08-11 22:22:32.0Z
From: <Pat Madigan>
Newsgroups: sybase.public.datawindow.net
References: <411a80a4$1@forums-1-dub> <v75lh0potd3vt0jpt9qvq9ak8th492n7cp@4ax.com>
Subject: Re: retrieval arguments in computed fields
Lines: 42
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1437
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
NNTP-Posting-Host: mail.gscutah.com
X-Original-NNTP-Posting-Host: mail.gscutah.com
Message-ID: <411a9c28$2@forums-1-dub>
Date: 11 Aug 2004 15:22:32 -0700
X-Trace: forums-1-dub 1092262952 208.11.90.3 (11 Aug 2004 15:22:32 -0700)
X-Original-Trace: 11 Aug 2004 15:22:32 -0700, mail.gscutah.com
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.datawindow.net:107
Article PK: 124543

Thanks, Jim. Too bad there's no Edit Source in the DW Designer, but the
export-import approach will get me there.

thanks,
Pat

"Jim O'Neil [Sybase]" <joneil_at_sybase_dot_com> wrote in message
news:v75lh0potd3vt0jpt9qvq9ak8th492n7cp@4ax.com...
> Yup, I see it to, but only in DataWindow Designer and not in
> PowerBuilder 10, which is rather odd since the code is very nearly the
> same.
>
> I see we disabled "Edit Source" in DataWindow Designer as well, but I
> was able to export, change the source, and import and the expression
> is working fine, it just doesn't pass validation in the painter. I'll
> log this as a bug.
>
> On 11 Aug 2004 13:25:08 -0700, <Pat Madigan> wrote:
>
> >When I try to use a retrieval argument in a computed field... even if the
> >only thing IN that expression is the retrieval argument... I hit the
verify
> >button and get an "Expression is not valid" error. This is the case for
new
> >retrieval arguments, as well as existing ones (when I imported a
datawindow
> >from my powerbuilder application).
> >
> >Has anyone else seen this? That's the only glitch I've seen so far. I
can't
> >believe how easy it was to throw a datawindow onto a WinForm, at least
for a
> >report.
> >
> >(My apologies for not taking part in the beta, where I could have caught
> >this sooner. I was on another assignment... no Powerbuilder.)
> >
> >Pat
> >
>