PvxPlus is here and continuing to develop! They just released ver 22!

Yes, it's working fine. Thank you!

Hi James,

Thanks for noticing this. It was due to some css styling.

The old truncating behaviour should now be used again after refreshing your browser page & cache by using shift-f5

There seems to be a slight change as to how the online manual presents itself. It still has the topics tree on the left and the reading pane on the right. However, when sliding the separator to the left, it now squeezes the tree instead of simply truncating the display of long descriptions.
Was this a conscious change? Personally, I would prefer the prior version.
Is it a browser thing? Currently using MS Edge Version 135.0.3179.98 (Official build) (64-bit).

Thanks for clarifying!

Keep up to date with what's happening at PVX Plus.  Please see our latest newsletter.

May 2025 Newsletter

Has anyone gotten Stamps.com software's ODBC to communicate both directions with a Px+ system? We'd been using 32-bit of each, and even with 8.1 Px+ SQL, the outbound-to-PX+ fails. and by 'fail', I mean Stamps crashes without showing an error, vanishes from the desktop, and checking the px+ ODBC log shows nothing touched it. We're planning to try both at 64 bit, but has anyone else tried?

Exactly

I personnally use 2 methods:

1- If the document is created from PVX, instead of creating a PDF, I write to the printer channel via "*WINPRT*"
2- If the printer is already built and just want to print it, I use a little program installed on the client machine or on the server (in your case your are printing from the server directly) called PDFtoPrinter and would call it from command line:

invoke hide "[lcl]c:\pathtoprogram\PDFtoPrinter.exe "+quo+FileName$+quo+" "+quo+PrinterInfo$+quo

Obviously, for either methods I need a database to keep the printers configuration for each workstations.  For example, you could need to print to printer1 for invoices, but print to printer2 for purchase orders.

Hello all. Using PxP 2024. This concerns the element written using the variable name Obj_Orig$ under a panel header (0000) rec in the panel library file.

I've noticed that in Library Compares, the reports are now starting to show

Customization was "panelAname"
                          now "panelBname"       [or one of the entries could be ""]

I examined the panel compare pgm, and I see that this is not a new thing; i.e. that "Customization" line has been in there for at least a few versions before 2024. And that Customization corresponds to Obj_Orig$.

My hunch is that panels edited now get the name of the panel written to Obj_Orig$ in its 0000 rec when saved in PxP 2024. Because when I looked at existing older panels, they have null in Obj_Orig$, whereas the ones edited in 2024 have it populated.

What's happening now as a consequence of this is that compared panels that normally do not have any differences between them now produce a report with that Customization as the only reported difference in the panel header section. Can someone explain why this is, why it's necessary?

Thanks!

Paula McKeever
CAI Software LLC

Ah, so I take the "Search All" means all of the elements represented by the checkboxes and nothing further?