Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Powerbuilder 10 migration errors (PFC)

277 views
Skip to first unread message

timcoffman

unread,
Jul 11, 2006, 10:50:48 AM7/11/06
to
I have a PowerBuilder 6.5 (PFC based)application that needs
to support
international characters. I have been trying to migrate to
PowerBuilder 10 with no success. I have successfully
migrated to power
8 and 9 with out much hassle.


When I went to 9 I had to fix some duplicate variable names
and get rid
of the trasnport object. When I try to migrate from 6.5 to
10 I get
thousands of lines of errors. I get the same errors if I
try to go
from PB 9 to 10 as well.


Everywhere I have read shows that this should be a simple
straight
forward process, I mean if I can convert my app to PB 9 why
in the
world do I get all these errors if I go to 10.


A sample of errors I am getting migrating to 10 from 9.


corpmain.pbl(corp_w_response).corp_w_response.pbm_syscommand.18:
Error
C0019: Incompatible property wordparm for type
powerobject
corpmain.pbl(corp_w_response).corp_w_response.pbm_syscommand.25:
Error
C0019: Incompatible property processed for type
powerobject
corpmain.pbl(corp_w_response).corp_w_response.pbm_syscommand.26:
Error
C0019: Incompatible property returnvalue for type
powerobject
corpmain.pbl(corp_w_response).corp_w_response.pbm_syscommand.30:
Error
C0019: Incompatible property processed for type
powerobject
corpmain.pbl(corp_w_response).corp_w_response.pbm_syscommand.32:
Error
C0019: Incompatible property returnvalue for type
powerobject
pfcmain.pbl(pfc_u_cb).pfc_u_cb.getfocus.30: Error
C0015:
Undefined variable: gnv_app
pfcmain.pbl(pfc_u_cb).pfc_u_cb.getfocus.30: Error
C0003:
Condition for if statement must be a boolean
pfcmain.pbl(pfc_u_cb).pfc_u_cb.getfocus.33: Error
C0003:
Condition for if statement must be a boolean
pfcmain.pbl(pfc_u_cb).pfc_u_cb.getfocus.36: Error
C0031: Syntax
error
pfcmain.pbl(pfc_u_st).pfc_u_st.getfocus.30: Error
C0015:
Undefined variable: gnv_app
pfcmain.pbl(pfc_u_st).pfc_u_st.getfocus.30: Error
C0003:
Condition for if statement must be a boolean
pfcmain.pbl(pfc_u_st).pfc_u_st.getfocus.33: Error
C0003:
Condition for if statement must be a boolean

Bruce Armstrong [TeamSybase]

unread,
Jul 11, 2006, 11:38:46 AM7/11/06
to
> Undefined variable: gnv_app

That means that the application you're using to do the migration doesn't
have gnv_app defined, whereas PFC references it. Are you sure you're
migrating the right application object?

> C0019: Incompatible property wordparm for type
> powerobject
> corpmain.pbl(corp_w_response).corp_w_response.pbm_syscommand.25:

It looks like your framework is expecting a custom message object, whereas
the application object you're migrating is still referencing a standard
message object. The question once again is if you are migrationg the right
application object.

<Tim Coffman> wrote in message news:44b3bac8.266...@sybase.com...

timcoffman

unread,
Jul 11, 2006, 2:38:15 PM7/11/06
to
I'm sure it is the correct application object. I copied the
PBLs from 6.5 to a version 10 directory, created a new
workspace and added the existing application and hit the
migrate button. What is odd is that this exact process
worked fine going to 9 from 6.5.

6.5 to 8 (no errors)
6.5 to 9 (fixed duplicate variable names and transport obj
references)
6.5 to 10 (Tons of errors)
9 to 10 (Tons of errors)

I do have global external functions in my application.
Would that cause my application to not be able to migrate to
10?

> > nd.18: Error


> > C0019: Incompatible property wordparm for type
> > powerobject
> >
> corpmain.pbl(corp_w_response).corp_w_response.pbm_syscomma

> > nd.25: Error


> > C0019: Incompatible property processed for type
> > powerobject
> >
> corpmain.pbl(corp_w_response).corp_w_response.pbm_syscomma

> > nd.26: Error


> > C0019: Incompatible property returnvalue for type
> > powerobject
> >
> corpmain.pbl(corp_w_response).corp_w_response.pbm_syscomma

> > nd.30: Error


> > C0019: Incompatible property processed for type
> > powerobject
> >
> corpmain.pbl(corp_w_response).corp_w_response.pbm_syscomma

> > nd.32: Error

Terry Voth

unread,
Jul 11, 2006, 2:54:59 PM7/11/06
to
The other thing the "absence" of gnv_app could indicate is a failure to compile
the application object. If that happens, the problem will cascade down to dozens
of objects. I'd suggest focusing on the application object errors, fixing those,
and trying again.

Good luck,

Terry [TeamSybase] and Sequel the techno-kitten

On 11 Jul 2006 07:50:48 -0700,
in sybase.public.powerbuilder.general

*********************************
PowerBuilder for $95? No.
Personal use PowerBuilder Enterprise *AND* PocketBuilder *AND* DataWindow.NET
*AND* Sybase IQ as free benefits of am ISUG membership. See
http://www.isug.com/ISUG3/Membership_benefits.html for details.

*********************************
Click once a day to help the hungry
http://www.thehungersite.com
*********************************
User Manual
===========
TeamSybase <> Sybase employee
Forums = Peer-to-peer
Forums <> Communication with Sybase
IsNull (AnswerTo (Posting)) can return TRUE
Forums.Moderated = TRUE, so behave or be deleted
*********************************

Sequel's Sandbox: http://www.techno-kitten.com
Home of PBL Peeper, a free PowerBuilder Developer's Toolkit.
Version 3.0.02 now available at the Sandbox
PB Futures updated Apr 24/2006
See the PB Troubleshooting & Migration Guides at the Sandbox
^ ^
o o
=*=

0 new messages