To ERR 65 or not to err 65

Started by Cees Trip, May 07, 2024, 08:00:26 AM

Previous topic - Next topic

Cees Trip

Hello all,

I'am puzzeld. We are, sadly, leaving pxplus behind for a ERP in Business Central. To keep access to our old pxplus files I purchased a 2 user pxplus windows licence. Now I am trying to get selected parts of out present programs working in windows.
Now I'm experiencing something crazy. Under the old version 12.500000 I don't get a error 65 when I create an existing window element multiple times. Also no error when making it visible, hide etc.
Under windows (version 20.100000) I do get an error 65. See Attachment.
Maybe I changed some in our old software at some point. I don't remember what, though. I would appreciate it if anyone could help me with this.
- personal is not the same as important - Terry Pratchett


Must be due to an upgrade in pxplus that causes this perhaps due to object properties?  I dont know if any PRM would help you here.

Can you add an err=*NEXT  to your controls...    This must be some legacy code?

0010 BEGIN
0020 MULTI_LINE 115,@(10,10,10,10)
0030 MULTI_LINE 115,@(10,10,10,10),ERR=*NEXT

Devon Austen

Both version 12.5 and version 20 normally return a error 65 if you try to use a control handle already in use.

Your PxPlus 12.5  likely has something in the START_UP that is making it ignore the error.

I would compare the START_UP of both versions and you may find your answer there.
Principal Software Engineer for PVX Plus Technologies LTD.

Mike King

Looking at what you posted you will notice that when the error was not reported you are connecting via WINDX whereas you get the error when connected directly.  You can tell this by the command line prompt -> versus -}.

If you have enabled WindX Turbo Mode (which is done be default in Nomads) duplicate CTL errors will not be reported back to the server but instead will be reported locally and reported only if the WindX setup enables local error reporting (default is not enabled).

WindX and Nomads are designed to maximize performance by running in Turbo Mode as no errors are anticipated.  This allow the system to run faster by not waiting for the WindX to report success or failure (much like UDP if you are familiar with that network protocol).
Mike King
President - BBSysco Consulting