This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
31
Language / Strange error 2
« on: December 08, 2020, 12:58:44 PM »
Customer running PVX 15.10. This line of code is throwing an error 2: 2060 read (slist,key=this_name$,dom=2020). Slist is a memory file. No special attributes. What would cause this to throw an error 2? I would think with a key specified (even if slits is 0 in length) the dom would trap an error 11.
32
ODBC / ODBC returning only 10 rows
« on: November 12, 2020, 01:13:51 PM »
I have pxpsql configured on a ReHat box and can query a table just fine with
/usr/pxpsqlodbc/pxpqsql -d /infor/facts78 "select Customer_num form AR_CUST_MAST where AR_CUST_MAST.company = '01'"
and the whole table dumps. On the other hand, in both my PxPlus environment, and the one from SDSI this only returns 10 rows before generating an error 2:
open(hfn)"[odb]FACTS;AR_CUST_MAST"
READ(LFO)*,CUST$;PRINT CUST$;GOTO *SAME
Any insight here is appreciated.
Michael
/usr/pxpsqlodbc/pxpqsql -d /infor/facts78 "select Customer_num form AR_CUST_MAST where AR_CUST_MAST.company = '01'"
and the whole table dumps. On the other hand, in both my PxPlus environment, and the one from SDSI this only returns 10 rows before generating an error 2:
open(hfn)"[odb]FACTS;AR_CUST_MAST"
READ(LFO)*,CUST$;PRINT CUST$;GOTO *SAME
Any insight here is appreciated.
Michael
33
Thin Client/WindX / *windev* generates error 12 trying to open printer
« on: October 20, 2020, 02:31:43 PM »
We have a user who as a printer defined on the server as link file P20, which contains "*windev*;SEA-P20". This has been working for years. Suddenly today, this printer can be accessed when connected to the server (windows 2012) directly, but when connecting through windx, even *from* the server, *windev* cannot be opened, nor an the printer P20. Throws an error 12. Any ideas what might have changed.
34
Programming / Binary auto increment key
« on: October 05, 2020, 04:29:27 PM »
I am having to set up a table that can be accessed from sql server. The schema I have been given to replicate has the primary key as an auto-increment bigint. I figure I can use the "I" option in a keydef and wind up with an adequate key as bigint is signed and the GUID type data involved is not, so 4 bytes would get me what I need. I can define a file such as 'keyed "test",[0:1:4:"I"),0,-1000' with no problem. My issue is how one write to is such that the key autoincrements. Michael
35
ODBC / pxpsql .ini config on linux
« on: July 31, 2020, 08:51:16 AM »
I am using pxpsql 6.0 on a linux box, querying data on the same box. I can easily access normalized tables defined in providex.ddf and .dde, but non-normalized tables as defined in a .ini file are not accessible. I don't know how to tell the command line what .ini file to use. Any input appreciated.
36
Programming / +B / -B behavior
« on: June 11, 2020, 11:45:36 AM »
I am attempting to cause a log file to not buffer. From what I can tell from the docs is that -B should be used in an open, like open(hfn,opt="-B")mylog.txt.
This does not seem to be working. Am I misinterpreting the documentation?
This does not seem to be working. Am I misinterpreting the documentation?
37
Language / Jaws Integration
« on: June 09, 2020, 12:50:58 PM »
We have a customer with some visually impaired employees (legally blind). The use a product called Jaws which can read information from a windows dialogue. I have to issues which I would like to get some input on. (PVX 15.1). Jaws can read the windows handle of various controls, but all windx windows are seen by it as having a handle of 0. Any ideas on why this would be? Jaws will also read tool tips. I have these set up, but as you know they only display when the mouse is hovering over the various controls. Is there a way to get these tool tips to display when the control has focus? This would solve the problem. From a 2000 ft perspective, has anyone worked with Jaws? Thanks! Michael
38
ODBC / PXPlus SQL ODBC Driver w/ Command line
« on: April 17, 2020, 10:51:28 AM »
I have attempted installing both the 7.00 and 6.10 version of the above on a Redhat 7 system.
cat os-release
NAME="Red Hat Enterprise Linux Server"
VERSION="7.8 (Maipo)"
ID="rhel"
ID_LIKE="fedora"
VARIANT="Server"
VARIANT_ID="server"
VERSION_ID="7.8"
PRETTY_NAME="Red Hat Enterprise Linux"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:redhat:enterprise_linux:7.8:GA:server"
HOME_URL="https://www.redhat.com/"
BUG_REPORT_URL="https://bugzilla.redhat.com/"
REDHAT_BUGZILLA_PRODUCT="Red Hat Enterprise Linux 7"
REDHAT_BUGZILLA_PRODUCT_VERSION=7.8
REDHAT_SUPPORT_PRODUCT="Red Hat Enterprise Linux"
REDHAT_SUPPORT_PRODUCT_VERSION="7.8"
From the command line I can do a list command and a select command with no problem, but as soon as I add a where clause I see this:
The driver reported the following diagnostics whilst running ODBCExecDirect
S0000:1:1019:[PxPlus][SQL ODBC Driver]Internal error
I added -l odbc.log and it has this:
Driver version: 7.00.0000
ISAMOpen: UserID='root', length=4
------------------------------
select company,library from SM_UNFORM_LIBRARY_PATHS where company = 01
GetAccessibleTables:<table=SM_UNFORM_LIBRARY_PATHS> Open catalog(s) /infor/facts78 , available 710 table(s)
<SM_UNFORM_LIBRARY_PATHS> Open file /infor/facts78/data/SM/SMUNFP, maxksz=20
ISAMCloseTable: Closing table SM_UNFORM_LIBRARY_PATHS - 0 file reads, 0 re-reads, 0 writes, 0 removes
CACHE STATS - 0 reads, size 2048 estimated, 0 used
ISAMClose
This is so close to working as I need it, but obviously this last needs to work.
Any input?
Michael
cat os-release
NAME="Red Hat Enterprise Linux Server"
VERSION="7.8 (Maipo)"
ID="rhel"
ID_LIKE="fedora"
VARIANT="Server"
VARIANT_ID="server"
VERSION_ID="7.8"
PRETTY_NAME="Red Hat Enterprise Linux"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:redhat:enterprise_linux:7.8:GA:server"
HOME_URL="https://www.redhat.com/"
BUG_REPORT_URL="https://bugzilla.redhat.com/"
REDHAT_BUGZILLA_PRODUCT="Red Hat Enterprise Linux 7"
REDHAT_BUGZILLA_PRODUCT_VERSION=7.8
REDHAT_SUPPORT_PRODUCT="Red Hat Enterprise Linux"
REDHAT_SUPPORT_PRODUCT_VERSION="7.8"
From the command line I can do a list command and a select command with no problem, but as soon as I add a where clause I see this:
The driver reported the following diagnostics whilst running ODBCExecDirect
S0000:1:1019:[PxPlus][SQL ODBC Driver]Internal error
I added -l odbc.log and it has this:
Driver version: 7.00.0000
ISAMOpen: UserID='root', length=4
------------------------------
select company,library from SM_UNFORM_LIBRARY_PATHS where company = 01
GetAccessibleTables:<table=SM_UNFORM_LIBRARY_PATHS> Open catalog(s) /infor/facts78 , available 710 table(s)
<SM_UNFORM_LIBRARY_PATHS> Open file /infor/facts78/data/SM/SMUNFP, maxksz=20
ISAMCloseTable: Closing table SM_UNFORM_LIBRARY_PATHS - 0 file reads, 0 re-reads, 0 writes, 0 removes
CACHE STATS - 0 reads, size 2048 estimated, 0 used
ISAMClose
This is so close to working as I need it, but obviously this last needs to work.
Any input?
Michael
39
Programming / List box column sort
« on: April 10, 2020, 02:19:47 PM »
I have a listview report style control for which I am trying to enable the lv'clickonhdrsort propery. I set that property to 1, and it reports back as one, but I do not get sorting. I'm sure there is another property that I need to adjust, but for the life of me I cannot figure out what it might be. I am seeing this at different PxPlus releases.
40
ODBC / ODBC fail w/ Office 2016 when using ORDER BY.
« on: March 25, 2020, 09:23:33 AM »
Customer is running ODBC 5.20.0002. Recently upgraded to Office 2016. Queries ran with earlier versions of excel that contained an "ORDER BY" clause. Now the are failing and reporting "[PxPlus][ODBC Driver][FILEIO]No data found. When the order by is removed the query executes. Has anyone dealt with this?
41
Programming / 2 gig string/serial file limit.
« on: February 05, 2020, 10:10:34 AM »
Has anyone figured out a clever way to bypass the limit on writing serial files larger than the 2 gig limit. I can do it with a shell script on *nix, but I don't really want to pursue that. I'd like something that is O/S agnostic and will work in *nix and windows.
42
ODBC / Unknown PXPIO Opcode - 0
« on: January 03, 2020, 10:42:16 AM »
Running PxPlus file server ver:5.20.0002 on linux I am getting the above error on one SQL query. Any insight as to what this might be telling me?
43
Language / File performance
« on: October 02, 2019, 04:20:27 PM »
I have a customer whose history files have years (10+) of history. Will this degrade overall performance. I process that they run daily is now taking a good deal longer than it used to and we are looking at ways to resolve this.
44
Programming / Weird programming result
« on: September 17, 2019, 10:45:11 AM »
On PxPlus 12.51 I see this:
2260 print (10)@(30),fnif(sorsop.type$="D",num(sorsop.orig_amt$),-num(sorsop.amount$)):y3$+" "+tbl(pos(sorsop.type$="DEORAT")-1,"",sorsop.reason$+" "+forfeit_reason$,"",sorsop.memo$,"",sorsop.note$); l=l+1; goto NEXT_DEP_TRANS
The contents of sorsop.memo$+sorsop.notes$ is ABCABCABCABCABCABC BLUE BUBBLES. All of the B's are dropped, whether printing to a device (notepad) or to the console. Note what should probably throw an error is that the first output is a masked numeric field passed through y3$ which is concatenated to a string value. Simply changing that "+" to a comma rectifies the issue. Attached doc shows this.
2260 print (10)@(30),fnif(sorsop.type$="D",num(sorsop.orig_amt$),-num(sorsop.amount$)):y3$+" "+tbl(pos(sorsop.type$="DEORAT")-1,"",sorsop.reason$+" "+forfeit_reason$,"",sorsop.memo$,"",sorsop.note$); l=l+1; goto NEXT_DEP_TRANS
The contents of sorsop.memo$+sorsop.notes$ is ABCABCABCABCABCABC BLUE BUBBLES. All of the B's are dropped, whether printing to a device (notepad) or to the console. Note what should probably throw an error is that the first output is a masked numeric field passed through y3$ which is concatenated to a string value. Simply changing that "+" to a comma rectifies the issue. Attached doc shows this.
45
Programming / Error 33's
« on: July 15, 2019, 10:45:30 AM »
I have a fairly straight forward loop of code that is throwing error 33's as it reads through larger files. Any pointers on how to check "remaining" memory, memory used, gosub/call stack size. I am not seeing anything which betrays a huge resource usage.