working fine in the IDE .but it crashing from 64bit deployed EXE
↧
Re: n_tooltip "Cannot register object in the toolwindow control" at Runtime (PB 12.6 x64)
↧
Re: Issues with Powerbuilder 12.6 .net version
Hi.
Partially supported means that powerbuilder during migration will import them, and they will possibly work, but you cannot add such controls in design when developing in powerbuilder.net. The normal way to do that in pb.net is to use 3rd party wpf controls! Of course in VS you have an option to add COM controls to your project. You have to reference them, as shown in following screenshot:
Im PB.NET the COM tab is missing...
But in PB.NET you cannot reference a com object the way you would do in C#. You can try to use a COM object with connecttoobject or connecttonewobject but it's not 100% that every control that you can use in PB Classic would work. Ex: for me excel partially works in pb.net using connecttoobject, but works fine in PB Classic.
Now those are limitations from .net framework. In VS you can add an active-x control. Actually it can host it through usinf the Windows Forms ActiveX Control Importer, thats why the SDK must be installed. PB.NET of course isn't implementing all functionallity available in VS. Example, in VS you can host a winform control in a wpf application. In pb.net you can't directly... OLE Active-x etc. are part of those limitations.
Follows what was mentioned in PB 12.1 help:
Because OLE controls are not used in .NET, we recommend using third-party controls or interop solutions instead. However, PowerBuilder provides limited support for OLE controls to help you migrate to .NET. Support for OLE controls has these limitations:
· No design-time support for inserting or inheriting from OLE controls to WPF applications.
· No support for dynamically creating OLE controls in PowerScript.
· No support for saving and retrieving the structured storage of an OLE control. Instead, users can set the initial value using a script.
· You can use most in-process OLE controls (OCX, DLL) in a WPF application, but you cannot use out-of-process OLE controls (EXE).
· Migration of 3rd party and OLE controls depends on their availability.
The .NET framework SDK 2.0 or later must be installed before you migrate OLE controls to WPF.
Now I don't know what controls you are using, but I would look if they are in-process controls. Also in the past I was told that to make an ole control work in WPF an ocx named tp4ole15.ocx has to be registered. It's found in \Program Files\Sybase\Shared\PowerBuilder path.
Andreas.
↧
↧
Re: SaveAS PDF not working with PB component in EAServer
Gentlemen,
The problem was resolved. It is related to registry, HKEY_USERS\.DEFAULT\Software\Microsoft\Windows NT\CurrentVersion\Devices\ was missing an entry "Sybase DataWindow PS" as Name and "winspool,FILE:" as Data.
It works perfectly now.
↧
Re: Why does getfullstate crash with nest datawindows?
Many years and releases ago, SetFullState failed if the blob had a filter buffer...
↧
Re: Print Datawindow to PDF file without using GhostScript
Is there a noticeable quality difference between the two?
↧
↧
Re: SaveAS PDF not working with PB component in EAServer
Hi Patrick;
I'm glad that you finally found the issue. 
I almost asked if your Sybase PS DataWindow printer & driver were installed properly ... but, you said "Standalone app is able to save to pdf file, not PB component in EAServer.". So I thought ... OK, that part must be there - so it must be something else.
Regards ... Chris
↧
Re: n_tooltip "Cannot register object in the toolwindow control" at Runtime (PB 12.6 x64)
I wonder if the problem is the structure byte alignment issue that was discussed here a couple days ago.
↧
Re: Print Datawindow to PDF file without using GhostScript
Not that I ever particularly noticed.
We were already using Amyuni when the PDF generation capability was added to PowerBuilder, so we didn't particularly use either.
I looked that the XSL-FO method as a potential to address the DataWindows issue with large text blocks. That's because the way you normally generate XSL-FO is with relative positioning and allow the renderer to flow everything onto the pages. However, when PowerBuilder generates XSL-FO, it specifies absolute positioning for everything. You get an exact rendering of what the datawindow looks like, which wasn't what I was trying to accomplish.
What we ended up doing was building our own emitter for the XLS-FO that used relative positioning. We also cross-compiled Apache FOP as a .Net assembly so we didn't have to deal with deploying a JRE, and called that assembly via a CCW.
↧
Re: Windows Task Manager - Get the Application Task Description?
please use instead ... cpollach at travel-net dot com
↧
↧
Re: Issues with Powerbuilder 12.6 .net version
Ankur Patel wrote:
Hello All,
I finally found the actual reason for those weird issues. It was giving error wherever we used ole control with POST. For example: ole_control.object.POST of_fuction(). Once I removed the post it stopped giving the error. I am not sure why POST would generate an error here.
I guess that this issue is related to the translation to c#...In a c# application an ole object is instanciated differently than in pb.net...
Error 16 Argument 2: cannot convert from 'ref object' to 'ref Sybase.PowerBuilder.PBLong' 76 119
Does anyone know how to get to the root cause of this error, because it does not show any file name. Is there a way to see the code that is converted by powerbuilder.net? because Sybase.PowerBuilder.PBLong looks like it belongs to C# code.
This seems to be a casting problem... Object is a different datatype than PBLong... Of course all powerbuilder type are descendants of System.Object... Don't know how to help you find where the error is located. Maybe searching the generated C# project would help you, but depending on the size of your application this could be a hard job...
Andreas.
↧
Re: Issues with Powerbuilder 12.6 .net version
Hello Andreas,
Thank you very much. Can you please tell me where is the generated c# project located. Because I didn't find anything like that in our project directory. There is a new folder wpf inside our application directory which has a folder for each pbl and all the PB objects are extracted inside those individual folders, but I didn't find any c# file.
Thanks,
Ankur Patel
↧
Re: Issues with Powerbuilder 12.6 .net version
Do you see any folder with .out extension?
↧
Re: LeadTools development in PB classic
We do use ImagXpress from Accusoft...
↧
↧
Re: LeadTools development in PB classic
↧
Re: LeadTools development in PB classic
No Chris. There are two products... The ImageGear and ImagXpress. Yes Pegasus and Accusoft merged some years ago. Actually when we was investigating which library to use we tested LeadTools, ImageGear and ImagXpress... We choose the last one, as we found it more productive with PB and in a reasonable cost.
Andreas.
↧
Re: Windows Task Manager - Get the Application Task Description?
Beautiful Chris, a BIG thank you - exactly what I was looking for! 
↧
Re: call store procedure from PB 12.5
Solution:
alter procedure DBA.PermisoDocumentoInventario(@usuario varchar(20),@Ingresar integer output
as
declare @Existe integer, @ingresar integer,
@Control char(1)
begin
select @Control = USER_CHEQ_NIVEL from
tb_data_seg_def_user where
USER_ID = @usuario and USER_STATUS = 'A'
if @Control = 'S'
begin
select @ingresar = COUNT(GRUS_ID) from
tb_data_seg_rel_grus where
GRUS_ID = @usuario and AUDI_COD_TRAN = '102001'
end
else
begin
select @Ingresar=1
end
select @ingresar
end
In the PB:
Declare wsp_permisoInventario procedure for PermisoDocumentoInventario
@usuario = :gs_user,
@Ingresar = :ii_ing output
using sqlca;
execute wsp_permisoInventario;
Fetch wsp_permisoInventario into :li_ingreso;
↧
↧
Re: Windows Task Manager - Get the Application Task Description?
That is Excellent news!
↧
Drop down calendar feature executable issue 12.6
In PB 12.6 (build 3506), there appears to be an issue with the drop down calendar feature. Functionality is different between development and executable PBD mode. The way it has been working for me in development mode is you open the calendar, click once in the header and you get a month selection for the current year, click again in the header (or double) and you get a selection of the year, click again and you get a selection of the decade. In run time mode sometimes a single click will give you a drop down type display of months (different GUI), but another click or two and then a click does nothing. ?
↧
Re: Drop down calendar feature executable issue 12.6
I realize now that if I click specifically on the title month (instead of any where on the title) I get the month drop down and if I click on the title year I get a year spin control. But the GUI is so different, why?
↧