When defining a catalog you can specify just a data dictionary. You can leave the ini field blank if you have no INI defining files.

What you specify in the data dictionary field is the path to the providex.ddf file that got created when you created a dictionary. This will be in your application directory likely with your other program files and data files.

For example if the DDF is located at C:\myapp\data\providex.ddf, then use C:\myapp\data.

The catalog is just telling the PxPlus SQL server where the data is. Defining it on the server means clients don't have to know where the data is and just point to a catalog to access the data defined in it.

Make sure the PxPlus SQL ODBC driver is the same version as the PxPlus SQL Server for compatibility. Older versions did not use the catalog and won't have the field.

Some descriptions of the different joins are found here: https://manual.pvxplus.com/?odbc/using_odbc_driver.htm
Some examples are foudn here: https://manual.pvxplus.com/?odbc/using_odbc_driver/example_sql.htm

My guess is this is what you want.

select * from { OJ (IM1_inventoryMasterFile  left outer join IMA_ProductLine   on IMA_ProductLine.ProductLineCode=IM1_inventoryMasterFile.productLine)  left outer join AP1_VendorMaster  on AP1_VendorMaster.VendorNumber=IM1_inventoryMasterFile.PrimaryVendorNumber  } where IM1_inventoryMasterFile.itemnumber=:pprod

Not that if you are using the PxPlus SQL ODBC driver version 6 or higher you can simplify  the syntax to remove the { oJ }

select * from (IM1_inventoryMasterFile  left outer join IMA_ProductLine   on IMA_ProductLine.ProductLineCode=IM1_inventoryMasterFile.productLine)  left outer join AP1_VendorMaster  on AP1_VendorMaster.VendorNumber=IM1_inventoryMasterFile.PrimaryVendorNumber where IM1_inventoryMasterFile.itemnumber=:pprod

I think you are right and that is a bug.

Please create a helpdesk ticket so we can properly track the bug and let you know when a fix is available.

This is just a guess but it sounds like what you are trying to access for your original test is not accessible from your machine. I would check firewall and to make sure you are on the correct network to access the resouce.

IT and ED+ are both good choices. ED+ is newer and was developed to provide a way that would work on the web and not just with Windows.

They both accomplish the same task and you can use the one that you are most comfortable with and you find the most useful.

You can also use both to edit the same file if you find there is a feature in one but not the other. Just use ED+ for the comment feature and do the rest of the editing in IT for example.

The issue was in the embedded chromium browser component so unfortunately you can't just grab an updated lib program from the new version. You will need to use version 19.10 for the fix. This can be done though with a version 18 license. It will just run with new v19.10 features disabled which should be fine since you just want the bug fix.

Is this on Windows or a UNIX/Linux. If UNIX/Linux what distributions are you running?

PxPlus supports TLS 1.2 as of version 14 (PxPlus 2017). Since you are using version 15.1 TLS 1.2 support is there so my guess is you are on a older Linux distribution that has an older OpenSSL without TLS 1.2.

You do say it worked with postman which I would assume also uses the OS OpenSSL so I could be wrong and something else like a bad install over an old PxPlus may be at play here. Or maybe postman has built-in OpenSSL?