I'm wondering if five years on someone might be able to answer my questions above

I'm looking at using the extended class validation feature define some data classes for use in a grid.

Lets say i create a class for 'Customer Code' which links to the customer file in the extended validation feature to verify the customer code is valid. I'm facing an issue with being able to specify that the value entered should be padded with spaces up to the maximum field length before checking the customer file (eg user enters 'CASH' but the key on the customer file is 'CASH  ' because all customer codes are padded to 6 characters.

Is there a way that I can't see to achieve this?

PERFECT! Thank you

Yes I am - as stated, the same connection string works fine with the pxpsql.exe command

FYI - same issue with something like:
LEFT JOIN 'INF09' ON INF31001+INF31002=INF09001

Having a problem using the OPT="CONNECT=" option when using OPEN [ODB] and trying to connect back to the PxPlus OBDC driver. It works fine with a DSN and the same connection string works with pxpsql.exe.

What am I doing wrong?

eg:
0010 LET CONNSTRING$="DRIVER={PxPlus® SQL ODBC Driver (64-bit)}; UID=A; PWD=B; DEBUG=1;Directory=D:\BBSCloud\BBSDev\DATA\DATA.BBS; Prefix=D:\BBSCloud\BBSDev\DATA\DATA.00,D:\BBSCloud\BBSDev\DATA\DATA.BBS,D:\BBSCloud\BBSDev\PROGS\PROGS.BBS; Company=00; LogFile=D:\BBSCloud\BBSDev\PXPSQLODBC.LOG; CacheSize=1024; DirtyReads=1; EnforceNULLDate=1; ReadOnly=1; SERVER=NotTheServer"
0020 OPEN (CHAN,OPT="CONNECT="+"'"+CONNSTRING$+"'")"[ODB]"

Returns:
IM002: [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified

I"ve tried all sorts of combinations around the CONNSTRING$ and cannot make it work.

However, the following command using the same connection string works perfectly.

"C:\PVX Plus Technologies\SQL ODBC Driver (64-bit)\pxpsql.exe" --connection-string "DRIVER={PxPlus® SQL ODBC Driver (64-bit)}; UID=A; PWD=B; DEBUG=1;Directory=D:\BBSCloud\BBSDev\DATA\DATA.BBS; Prefix=D:\BBSCloud\BBSDev\DATA\DATA.00,D:\BBSCloud\BBSDev\DATA\DATA.BBS,D:\BBSCloud\BBSDev\PROGS\PROGS.BBS; Company=00; LogFile=D:\BBSCloud\BBSDev\PXPSQLODBC.LOG; CacheSize=1024; DirtyReads=1; EnforceNULLDate=1; ReadOnly=1; SERVER=NotTheServer" "SELECT * FROM ARF12"

The below query is very slow to execute (approx one row per second), as if it is reading the entire INF11M data file for each INF04M record. INF04001 contains the invoice number (1,6) and line number (7,3) and INF11001 is the invoice number which is the primary key of INF11M.

The only way we can see to join the headers (INF11M) to the lines (INF04M) is to use the SUBSTR function. Is there a better way?

SELECT * FROM 'INF04M' LEFT JOIN 'INF11M' INF11M ON INF11001=SUBSTR(INF04001,1,6)

Both files are KEYED files. INF11M has ~84,000 records.

When joining tables, we have discovered a massive performance difference between using the native SELECT WITH command vs ODBC LEFT JOIN on native PxPlus files.

Attached are three test programs. You won't be able to run them without the data files or dictionary, but you'll be able to see what we are doing.

File INF31 has approximately 300,000 records, and the fields being restricted are not within a key so the entire file is being read. APF00 has 310 records, the field being joined on is the primary key of APF00.

With the native SELECT WITH, the process takes 10 minutes to return the results. With the pxpsql.exe command line utility, or the [OBD] tag to read the data via the ODBC driver, results are returned in less than a second.

All three queries return the same results.

Why would this be?

Hey jdegrendele,

We had the same issue with RemoteApp on Server 2022 but we don't think it is specifically PxPlus related. It may be because most of us likely use pop-up dialogs that aren't within a main application window that RemoteApp gets the focus incorrect.

Others are complaining too https://www.reddit.com/r/sysadmin/comments/11pzji9/server_2022_remote_app_issues/

We just rolled out new 2019 RDS servers in Azure, with our fingers crossed that the issues will be fixed in the next Windows Server version...

Hi Mike,

PKG revealed that my license was still running at activation level 18.

Running *plus/reg/net appears to have upgraded the activation to level 19 and now i can see the OnDoubleClick property.

Thanks and sorry to waste your time!

Chris

HI Mike,

Thanks for that. I've downloaded v19.1 and cannot seem to get the OnDoubleClick property to accept a value for either manually created controls or controls created in nomads.

Code:
0010 LET MY_MULTILINE=5
0020 MULTI_LINE MY_MULTILINE,@(50,5,10,1)
0030 LET MY_MULTILINE'ONDOUBLECLICK=5000

Results in an Err #88.

Image attached.

Have I missed something?

Wow Mike, that is amazing news.

Thank you heaps!

I'll keep a look out for Update 1!

Hi Mike,

I'm thinking about changing some of my multilines to behave like hotlinks currently do in list boxes.

For example, a locked multi-line that displays a customer code and name. The user can currently click and highlight to copy the text, and i was hoping to implement logic so if they double click it will take them to view more details about the customer (ie open a customer enquiry). This saves me having buttons everywhere for users to navigate to different areas when looking at a transaction.

Understand if it isn't possible with the options currently available, but thought i'd ask since you can acheive this in VB.

Hi All,

Simple question that I think the answer is No but thought I'd ask.

Is there a way to set the attributes in such a way to fire the focus or on-change event when a multi-line control is double-clicked on?

I've tried IF POS($020D$:_EOM$)<>0  then MSGBOX "Test" in the on focus logic but it only executes when focus is first given to the control. On change doesn't appear to fire on a double click even when Auto and Signal on Exit are enabled.

Thanks
Chris

Hi All,

I cannot seem to get the TinyMCE spell check functionality working on v18.1 in nomads using the provided control. I'm using the standard built-in extended layout. Any ideas?

See attached.

Chris