从Powerbuilder 6.5迁移到10.5 [英] Migrating from Powerbuilder 6.5 to 10.5

问题描述

我们有一个使用PFC构建的应用程序.我面临一个奇怪的问题.当我定义工作区并仅打开PFC库时，我可以迁移并进行完整的构建.但是，当我将其包含在应用程序库中时，它将无法构建，并给我一个错误，指出C0001:数据类型s_printsetupattrib非法.

We have an application that is built using PFC. I am facing a strange problem. When I define a workspace and open only the PFC librares, I can migrate and do a full Build. However, when I include this in my application library, it will not build, and gives me an error stating C0001: Illegal datatype s_printsetupattrib.

无论在何处使用都将发生此错误.

This error occurs wherever it is used.

Google尚未给出任何答案.我试图在pfcapsrv.pbl中重新生成s_printsetupattrib，并且它可以重新生成.我尝试的下一步是重新生成pfc_n_cst_platform(pfcapsrv.pbl)和其他此类对象，但这些对象不会重新生成，并引发此错误.

Googling hasn't given any answers. I have tried to regenerate s_printsetupattrib within the pfcapsrv.pbl, and it regenerates fine. The next step I tried was to regenerate pfc_n_cst_platform (pfcapsrv.pbl), and other such objects, but these do not regenerate, and throw this error.

需要在应用程序迁移库列表中列出pbl的顺序是什么?

Is there anything in the sequence in which the pbl need to be listed in the application migration library list?

在此问题上的任何帮助，我将不胜感激.

I will appreciate any help in the matter.

关于， 恩德赛.

推荐答案

我注意到这个问题已过时，但由于您没有真正得到答案，所以添加了2美分.

I noticed this question is dated, but adding my 2cents since you didn't really get an answer.

如果您使用的是项目对象，然后从那里执行构建部署"，并指定了完整构建"，则PB会自动以正确的顺序编译内容，除非您有重复的对象名称，否则无需按顺序进行编译这不是最好的主意.我猜我建议您检查一下以确保您的PBL中也没有重复的对象.

If you are using a project object, and perform the build "deploy" from there and "full build" is specified then PB automatically compiles things in the right order, no need to put things in order unless you have duplicate object names which isn't the best idea. I guess I'd recommend checking to make sure you don't have duplicate objects in your PBL's also.

如果您仍然遇到问题，那么我会遇到PB编译器感到困惑的问题，例如自引用情况或其他复杂情况，并且它是PITA，大多数情况下，这种情况在设计上还是很糟糕，因此请尝试理解正在修改代码，不是您想听到的，而是发生了事情.

If you still run into problems I've had problems where PB compiler gets confused like self referencing situations or other complex situations and it's a PITA, most the time this happens it is something that was poorly designed anyway so try to understand what is going on and modify the code, not what you want to hear but stuff happens.

或者...作为另一种解决方法，我们遇到了无法正确编译的故障代码，当它失败时，您会发现无法编译的对象(在您的情况下，是引用结构的对象)并使用文件->开源，找到引用该结构的代码，并在可行的情况下将其注释掉，然后尝试重新编译.一切编译完成后，打开手动注释的对象并进行编译.

Or... as another workaround we've had trouble code that doesn't compile properly and when it fails, you find the object that won't compile (in your case the one referencing the structure) and open it with file--> open source, find code referencing the structure and if feasible comment it out and try the recompile. After everything compiles open the manually commented object and compile.

您所描述的并不少见，有时您必须变得很有创意，尤其是在使用过时的PFC时.

What you are describing isn't totally uncommon, sometimes you have to get creative especially when using the dated PFC.

此致， 丰富

这篇关于从Powerbuilder 6.5迁移到10.5的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！