Show Posts
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.
76
Programming / Re: Calendar on Multi-Line
« on: December 16, 2020, 09:03:31 AM »
See the PxPlus manul under Multi_line, or search on calendar:
The Calendar feature may be set up using the HLP= option as follows:
MULTI_LINE ctl_id, @(col,ln,wth,ht)),HLP="[Calendar]parameters$"
The parameter list (parameters$) can consist of any of the following options separated by semi-colons:
CALENDAR=YES | NO
YES turns on the Calendar support. NO turns it off. Default is NO.
CONTENTS=string$
Text or graph appearing on the button. Default is "{!DATE}".
DTE=date$
Date formatting rules. Default is based on the DTE( ). Semi-colon cannot be part of this parameter. (If used, the string following will be ignored.)
Date code should include % percent; however, if not used, input will be parsed based on format provided. If a time formatting string is included, the current time is used.
HEIGHT=num
Height of the button. Default is the height defined for MULTI_LINE.
SHOWBUTTON=YES | NO
YES shows the Calendar button. NO hides it. Default is YES.
WIDTH=num
Width of the button. Default width is equal to the height defined for the MULTI_LINE; i.e. the default size is a square.
The 'Calendar$ property can also be used (with the above parameter list):
ML_Ctl'Calendar$="CALENDAR=YES;DTE=%Y%M%D;Contents={!Stop}Stop;Width=10".
When invoked, the top border of the calendar popup will be aligned with the bottom border of the multi-line input area. If parameters are not specified, the default button contents will be {!DATE} and the width and height of the button equal to the height of the control itself.
The following methods can be used to invoke the calendar:
•When the multi-line input area has focus, press Shift-F2. In this case, CTL=-6 is suppressed.
•Use the mouse or touchpad to click on the calendar button.
The calendar will disappear automatically when:
•A date is selected and placed in the multi-line input area.
•An ESC is pressed.
•The user clicks anywhere outside the button or calendar.
When the button is clicked, no EOM value will be generated, as the button is considered part of the MULTI_LINE directive and is handled internally. When a date is inserted into the multi-line input area, no EOM value will be generated unless OPT="A" has been set and focus is on the MULTI_LINE control.
The calendar popup displays the following features:
•A grid-like format makes it easy to distinguish the days of the month.
•The text and background of the current date, as well as the current selection, are presented in a different color for clear identification.
•Previous/Next month arrow buttons allow the user to browse through the months of the currently selected year.
•To see the entire month at a glance, the last day(s) of the previous month and the first day(s) of the next month are displayed.
When the MULTI_LINE is hidden or disabled, the calendar button should also be hidden or disabled, and Shift-F2 will not display the calendar control.
Example:
The following code sample invokes the Calendar feature using both methods: the HLP= string and the Calendar$ property.
0010 PRINT 'DIALOGUE'(0,0,100,50,"test",OPT="*Z")
0020 PRINT '4D','CS'
0030 LET A=1000
0040 MULTI_LINE A,@(10,10,30,1),HLP="[CALENDAR]CALENDAR=YES"
0050 LET B=1001
0060 MULTI_LINE B,@(10,20,30,1)
0070 LET B'CALENDAR$="CALENDAR=YES;DTE=%Y %Ml %D;Contents=Enter Date;Width=10"
0080 PRINT "A: ",A'CALENDAR$
0090 PRINT "B: ",B'CALENDAR$
0100 OBTAIN (0,SIZ=1)'ME',A$,'MN',; LET C=CTL; LET E$=HTA(EOM); PRINT "CTL=",C," EOM=",E$
0110 IF C=4 THEN ESCAPE
0120 GOTO 0100
The Calendar feature may be set up using the HLP= option as follows:
MULTI_LINE ctl_id, @(col,ln,wth,ht)),HLP="[Calendar]parameters$"
The parameter list (parameters$) can consist of any of the following options separated by semi-colons:
CALENDAR=YES | NO
YES turns on the Calendar support. NO turns it off. Default is NO.
CONTENTS=string$
Text or graph appearing on the button. Default is "{!DATE}".
DTE=date$
Date formatting rules. Default is based on the DTE( ). Semi-colon cannot be part of this parameter. (If used, the string following will be ignored.)
Date code should include % percent; however, if not used, input will be parsed based on format provided. If a time formatting string is included, the current time is used.
HEIGHT=num
Height of the button. Default is the height defined for MULTI_LINE.
SHOWBUTTON=YES | NO
YES shows the Calendar button. NO hides it. Default is YES.
WIDTH=num
Width of the button. Default width is equal to the height defined for the MULTI_LINE; i.e. the default size is a square.
The 'Calendar$ property can also be used (with the above parameter list):
ML_Ctl'Calendar$="CALENDAR=YES;DTE=%Y%M%D;Contents={!Stop}Stop;Width=10".
When invoked, the top border of the calendar popup will be aligned with the bottom border of the multi-line input area. If parameters are not specified, the default button contents will be {!DATE} and the width and height of the button equal to the height of the control itself.
The following methods can be used to invoke the calendar:
•When the multi-line input area has focus, press Shift-F2. In this case, CTL=-6 is suppressed.
•Use the mouse or touchpad to click on the calendar button.
The calendar will disappear automatically when:
•A date is selected and placed in the multi-line input area.
•An ESC is pressed.
•The user clicks anywhere outside the button or calendar.
When the button is clicked, no EOM value will be generated, as the button is considered part of the MULTI_LINE directive and is handled internally. When a date is inserted into the multi-line input area, no EOM value will be generated unless OPT="A" has been set and focus is on the MULTI_LINE control.
The calendar popup displays the following features:
•A grid-like format makes it easy to distinguish the days of the month.
•The text and background of the current date, as well as the current selection, are presented in a different color for clear identification.
•Previous/Next month arrow buttons allow the user to browse through the months of the currently selected year.
•To see the entire month at a glance, the last day(s) of the previous month and the first day(s) of the next month are displayed.
When the MULTI_LINE is hidden or disabled, the calendar button should also be hidden or disabled, and Shift-F2 will not display the calendar control.
Example:
The following code sample invokes the Calendar feature using both methods: the HLP= string and the Calendar$ property.
0010 PRINT 'DIALOGUE'(0,0,100,50,"test",OPT="*Z")
0020 PRINT '4D','CS'
0030 LET A=1000
0040 MULTI_LINE A,@(10,10,30,1),HLP="[CALENDAR]CALENDAR=YES"
0050 LET B=1001
0060 MULTI_LINE B,@(10,20,30,1)
0070 LET B'CALENDAR$="CALENDAR=YES;DTE=%Y %Ml %D;Contents=Enter Date;Width=10"
0080 PRINT "A: ",A'CALENDAR$
0090 PRINT "B: ",B'CALENDAR$
0100 OBTAIN (0,SIZ=1)'ME',A$,'MN',; LET C=CTL; LET E$=HTA(EOM); PRINT "CTL=",C," EOM=",E$
0110 IF C=4 THEN ESCAPE
0120 GOTO 0100
77
Language / Re: Strange error 2
« on: December 10, 2020, 09:05:12 AM »
Mike,
My mistake. It was PxPlus 15.10. We only run PxPlus at this point.
Michael
My mistake. It was PxPlus 15.10. We only run PxPlus at this point.
Michael
78
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.
79
ODBC / Re: ODBC returning only 10 rows
« on: November 12, 2020, 05:17:26 PM »
Devon, I checked my system and there in only one DSR configured on the unix server where our PxPlus executable is running; Unform is running on the same server, so it has no way to see other than the linux configured ODBC. Also, debug is on. Wouldn't the log show if it is accessing in Demo mode?
80
ODBC / Re: ODBC returning only 10 rows
« on: November 12, 2020, 04:53:19 PM »
Thanks Devon. That 10 row limit was familiar because I configured and tested before I got the license. Just wasn't sure why/how to point to the correct spot. I will check based on your feedback.
81
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
82
Thin Client/WindX / Re: *windev* generates error 12 trying to open printer
« on: October 21, 2020, 02:26:04 PM »
So this is back as in issue. It appears that if I edit a device (change a driver for example), then access to *windev* fails *only for those who are accessing through WindX. If I am on the server and directly into Pxplus I can access *windev*. If I am on the server, but use a client, it is a no go.
83
Thin Client/WindX / Re: *windev* generates error 12 trying to open printer
« on: October 20, 2020, 03:42:09 PM »
Going to cancel this. Reboot solved problems so typical windows issue.
84
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.
85
Programming / Re: Binary auto increment key
« on: October 07, 2020, 09:11:10 AM »
Gord - Thanks for the response, but this is simply not working for me. Can you send a code snippet that works? Michael
86
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
87
Programming / Re: Piped character count
« on: September 04, 2020, 10:34:21 AM »
James,
I would be interested if there is an internal value that tracks this, but I just use a variable, reset a the time of Pipe open, and add the size (len) of the payload before I write it to the pipe channel.
Michael
I would be interested if there is an internal value that tracks this, but I just use a variable, reset a the time of Pipe open, and add the size (len) of the payload before I write it to the pipe channel.
Michael
88
ODBC / Re: pxpsql .ini config on linux
« on: August 07, 2020, 11:46:42 AM »
Devon,
The Docs don't reference the IniFile option, so that made it hard to ferret out. Anyway, here is my DSN:
[FACTS]
Driver=PxPlus
Description=FACTS Data
Directory=/infor/facts78
IniFile=/infor/facts78/dict/FACTSDD.INI
Debug=1
LogFile=/tmp/odbc.log
I still get "File is not accessible". Any other insight? I have worked around this, but would like to get it resolved if possible against future need. - thanks!
The Docs don't reference the IniFile option, so that made it hard to ferret out. Anyway, here is my DSN:
[FACTS]
Driver=PxPlus
Description=FACTS Data
Directory=/infor/facts78
IniFile=/infor/facts78/dict/FACTSDD.INI
Debug=1
LogFile=/tmp/odbc.log
I still get "File is not accessible". Any other insight? I have worked around this, but would like to get it resolved if possible against future need. - thanks!
89
ODBC / Re: pxpsql .ini config on linux
« on: July 31, 2020, 11:42:06 AM »
Devon,
Perhaps I didn't explain that correctly. I have configured ODBC into unixODBC. In that context I don't know how to get an .ini file into use. Michael
Perhaps I didn't explain that correctly. I have configured ODBC into unixODBC. In that context I don't know how to get an .ini file into use. Michael
90
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.