Hi Yakov;

  Correct .. the PB.NET object class' source code is not compatible with PB Classic (which Appeon PB is based on). AFAIK, there is no magic reverse compiler from PB.Net back over to PB Classic. Therefore, its a completely manual process. Because the syntax it different, a suspect a lot of "seat of the pants" (trial & error) syntax changes  would be required.    :-(

Regards .. Chris

Just found this : Line numbers in datawindow import error: how do they compare to line numbers in a text editor? (appeon.com)

Hi Yakov,

it looks like a Composite Datawindow with retrieval arguments.
Try to change unbound=yes to unbound="yes".

hth

Arnd

Thanks you to all who offered suggestions

So far I found two issues. 

One is a new keyword

 unbound is not significant in Classic DWs  I think the .net dw painter just put it in automatically.  I deleted it and its value

>In generic .NET, setting unbound=yes typically means that the DataSet is not directly bound to a database.  This allows you to manually populate with data from other sources, such as arrays, collections, or other non-database sources, which was useful when you need to display data that doesn't come from a traditional database or when you want more control over how data is loaded and managed within the DataWindow. <<

The one I am repairing now has a SP execute in the syntax.

The other was a Sybase DWO syntax developer slip

Sybase added " " around   name  and slideup values for line object