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.

Migrating Datawindows

4 posts in DataWindow Last posting was on 2008-11-04 14:43:36.0Z
Rick Post Posted on 2008-11-03 16:42:42.0Z
Sender: 573d.490f2335.1804289383@sybase.com
From: Rick Post
Newsgroups: sybase.public.powerbuilder.datawindow
Subject: Migrating Datawindows
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <490f2a02.57b9.1681692777@sybase.com>
NNTP-Posting-Host: 10.22.241.41
X-Original-NNTP-Posting-Host: 10.22.241.41
Date: 3 Nov 2008 08:42:42 -0800
X-Trace: forums-1-dub 1225730562 10.22.241.41 (3 Nov 2008 08:42:42 -0800)
X-Original-Trace: 3 Nov 2008 08:42:42 -0800, 10.22.241.41
Lines: 14
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.powerbuilder.datawindow:88093
Article PK: 417348

We have datawindow syntax stored in the database for
user-defined reports and forms, etc. Our current clients are
running an application written in PB 9.0 and they want to
upgrade to our 11.0 version. The problem is that the DW
syntax is in PB 9.0 format and we get an invalid version
error when reading the syntax out of the database and trying
to create a datawindow in the PB 11.0 app.

Does anybody know of a way we could programmatically migrate
the DW syntax? Some of our clients could have a hundred
thousand filled-out forms saved in the database.

Thank you!
Rick


Jeremy Lakeman Posted on 2008-11-03 23:10:46.0Z
From: Jeremy Lakeman <jeremy.lakeman@gmail.com>
Newsgroups: sybase.public.powerbuilder.datawindow
Subject: Re: Migrating Datawindows
Date: Mon, 3 Nov 2008 15:10:46 -0800 (PST)
Organization: http://groups.google.com
Lines: 30
Message-ID: <df3ebd2f-6636-419d-841f-96abad81c2d0@i18g2000prf.googlegroups.com>
References: <490f2a02.57b9.1681692777@sybase.com>
NNTP-Posting-Host: 203.122.242.105
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Trace: posting.google.com 1225753846 15648 127.0.0.1 (3 Nov 2008 23:10:46 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: Mon, 3 Nov 2008 23:10:46 +0000 (UTC)
Complaints-To: groups-abuse@google.com
Injection-Info: i18g2000prf.googlegroups.com; posting-host=203.122.242.105; posting-account=euaBtgoAAAC_vDxfsxmpMKlBxHaHpmRS
User-Agent: G2/1.0
X-HTTP-UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.3) Gecko/2008092417 Firefox/3.0.3,gzip(gfe),gzip(gfe)
X-HTTP-Via: 1.1 fly.essential.com.au:3128 (squid/2.5.STABLE8), 1.0 asp.essential.intranet:3128 (squid/2.5.STABLE8)
Path: forums-1-dub!forums-master!newssvr.sybase.com!news-sj-1.sprintlink.net!news-peer1.sprintlink.net!nntp1.phx1.gblx.net!nntp.gblx.net!nntp.gblx.net!border2.nntp.dca.giganews.com!nntp.giganews.com!postnews.google.com!i18g2000prf.googlegroups.com!not-for-mail
Xref: forums-1-dub sybase.public.powerbuilder.datawindow:88095
Article PK: 417351


On Nov 4, 2:42 am, Rick Post wrote:
> We have datawindow syntax stored in the database for
> user-defined reports and forms, etc. Our current clients are
> running an application written in PB 9.0 and they want to
> upgrade to our 11.0 version. The problem is that the DW
> syntax is in PB 9.0 format and we get an invalid version
> error when reading the syntax out of the database and trying
> to create a datawindow in the PB 11.0 app.
>
> Does anybody know of a way we could programmatically migrate
> the DW syntax? Some of our clients could have a hundred
> thousand filled-out forms saved in the database.
>
> Thank you!
> Rick

That's a new one. I've never had a problem using old datawindow report
syntax on a new version of powerbuilder. Going the other way never
works of course.

What doesn't work between versions is PowerSoft Report (.psr) files.
I'll assume that's what you meant.

You'll need to write a PB9 application to load the psr and save it to
a different format. I would suggest creating pdf's instead as the
format is not tied to any version of PB.

You can either create an application to batch convert all the objects,
or deploy a PB9 nvo and call it via ole to do the conversion on the
fly.


KL Posted on 2008-11-04 14:24:47.0Z
Sender: 619b.490f8140.1804289383@sybase.com
From: KL
Newsgroups: sybase.public.powerbuilder.datawindow
Subject: Re: Migrating Datawindows
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <49105b2f.1a8.1681692777@sybase.com>
References: <df3ebd2f-6636-419d-841f-96abad81c2d0@i18g2000prf.googlegroups.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
NNTP-Posting-Host: 10.22.241.41
X-Original-NNTP-Posting-Host: 10.22.241.41
Date: 4 Nov 2008 06:24:47 -0800
X-Trace: forums-1-dub 1225808687 10.22.241.41 (4 Nov 2008 06:24:47 -0800)
X-Original-Trace: 4 Nov 2008 06:24:47 -0800, 10.22.241.41
Lines: 33
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.powerbuilder.datawindow:88099
Article PK: 417353

Note: Sometimes you can 'go back' by carefully editing the
DW source. KL

> On Nov 4, 2:42 am, Rick Post wrote:
> > We have datawindow syntax stored in the database for
> > user-defined reports and forms, etc. Our current clients
> > are running an application written in PB 9.0 and they
> > want to upgrade to our 11.0 version. The problem is that
> > the DW syntax is in PB 9.0 format and we get an invalid
> > version error when reading the syntax out of the
> > database and trying to create a datawindow in the PB
> 11.0 app. >
> > Does anybody know of a way we could programmatically
> > migrate the DW syntax? Some of our clients could have a
> > hundred thousand filled-out forms saved in the database.
> >
> > Thank you!
> > Rick
>
> That's a new one. I've never had a problem using old
> datawindow report syntax on a new version of powerbuilder.
> Going the other way never works of course.
>
> What doesn't work between versions is PowerSoft Report
> (.psr) files. I'll assume that's what you meant.
>
> You'll need to write a PB9 application to load the psr and
> save it to a different format. I would suggest creating
> pdf's instead as the format is not tied to any version of
> PB.
>
> You can either create an application to batch convert all
> the objects, or deploy a PB9 nvo and call it via ole to do
> the conversion on the fly.


Rick Post Posted on 2008-11-04 14:43:36.0Z
Sender: 7b16.49104e6a.1804289383@sybase.com
From: Rick Post
Newsgroups: sybase.public.powerbuilder.datawindow
Subject: Re: Migrating Datawindows
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <49105f98.39a.1681692777@sybase.com>
References: <df3ebd2f-6636-419d-841f-96abad81c2d0@i18g2000prf.googlegroups.com>
NNTP-Posting-Host: 10.22.241.41
X-Original-NNTP-Posting-Host: 10.22.241.41
Date: 4 Nov 2008 06:43:36 -0800
X-Trace: forums-1-dub 1225809816 10.22.241.41 (4 Nov 2008 06:43:36 -0800)
X-Original-Trace: 4 Nov 2008 06:43:36 -0800, 10.22.241.41
Lines: 30
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.powerbuilder.datawindow:88100
Article PK: 417355


>
> That's a new one. I've never had a problem using old
> datawindow report syntax on a new version of powerbuilder.
> Going the other way never works of course.
>
> What doesn't work between versions is PowerSoft Report
> (.psr) files. I'll assume that's what you meant.
>
> You'll need to write a PB9 application to load the psr and
> save it to a different format. I would suggest creating
> pdf's instead as the format is not tied to any version of
> PB.
>
> You can either create an application to batch convert all
> the objects, or deploy a PB9 nvo and call it via ole to do
> the conversion on the fly.

It is actually datawindow syntax, not PSRs. However, I found
out what the problem was. It wasn't a release number
problem, it was the encoding of the blob in the database. We
also upgraded from sql server 2000 to sql server 2005 (MS).

To fix it, after doing the SELECTBLOB, I convert it to a
string using this syntax:

l_cForm = string(l_blForm, EncodingANSI!)

instead of using the default UTF16 encoding.

Problem solved! Thanks for the replies.