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.
901
Registration and Setup / Re: Error #99
« on: August 24, 2018, 04:51:06 PM »
This sounds like your activation keys are for a earlier release or you have not registered your product yet.
When you first install PxPlus you are provided a temporary installation keys which allows you to run for 30 days. There are generally two keys provided, one which unlocks basic functionality which is enough to get the system up so it can register and a second key that adds a number of PxPlus exclusive features.
Either the keys you are using are for a prior release, or you are running on a single temporary installation key and have not registered your product.
When you first install PxPlus you are provided a temporary installation keys which allows you to run for 30 days. There are generally two keys provided, one which unlocks basic functionality which is enough to get the system up so it can register and a second key that adds a number of PxPlus exclusive features.
Either the keys you are using are for a prior release, or you are running on a single temporary installation key and have not registered your product.
902
Programming / Re: Sort By Header Question
« on: August 23, 2018, 09:48:04 PM »
Not certain why you need either signal all or on focus.
Setting SortOnHdrClick to zero generates a normal grid change event when a column header is clicked as these are treated like buttons.
Setting SortOnHdrClick to zero generates a normal grid change event when a column header is clicked as these are treated like buttons.
903
Language / Re: Radio Button Logic
« on: August 23, 2018, 02:44:37 PM »
Events are only associated with primary radio button of a group -- that is index 1.
In addition the FOCUS event treats the focus to any of the radio buttons in the group together, that is it fires the logic assigned to the on focus logic of the primary button when any button gets focus HOWEVER changing focus from button to button within the group is not fire an on focus event.
So for example if I have three radio buttons:
(o) Visa
(o) MasterCard
(o) Amex
If I put focus from any control outside of the radio button group to any of the radio buttons I will get the on focus event, but if once in group and focus is for example on Visa, changing focus to Amex or MasterCard will no fire an on focus event.
All buttons in a radio button group are considered as a single control.
In addition the FOCUS event treats the focus to any of the radio buttons in the group together, that is it fires the logic assigned to the on focus logic of the primary button when any button gets focus HOWEVER changing focus from button to button within the group is not fire an on focus event.
So for example if I have three radio buttons:
(o) Visa
(o) MasterCard
(o) Amex
If I put focus from any control outside of the radio button group to any of the radio buttons I will get the on focus event, but if once in group and focus is for example on Visa, changing focus to Amex or MasterCard will no fire an on focus event.
All buttons in a radio button group are considered as a single control.
904
Programming / Re: Sort By Header Question
« on: August 23, 2018, 02:10:12 PM »
Generally a Grid will sort in under a few seconds assuming a reasonable number of rows. On my local PC a grid with 1000 rows sort virtually instantaneously whereas 5000 takes about 3 seconds. Sort time will vary based on the randomness of the data.
You can also handle the sort request yourself and display something for the duration or as shown in the example below change the column header to RED for the duration.
You can also handle the sort request yourself and display something for the duration or as shown in the example below change the column header to RED for the duration.
Code: [Select]
0010 PRINT 'CS',
0020 GRID 10,@(5,1,40,10),SEP=","
0030 LET x=10
0040 LET x'sortonhdrclick=0
0050 FOR i=1 TO 10000
0060 GRID LOAD 10,0,i,STR(RND(1000)*i:"00000000")+",Item "+STR(i)+","
0070 NEXT i
0080 PRINT "Ready to sort"
0090 WHILE 1
0100 OBTAIN (0)*
0110 IF CTL=4 OR EOM=ESC THEN BREAK
0120 IF CTL<>x THEN CONTINUE
0130 GRID READ x,col,row,eom$
0140 IF row<>-1 THEN CONTINUE
0150 LET x'colno.row.backcolour.$=STR(col)+SEP+STR(row)+SEP+"Lite Red"+SEP
0160 WAIT .1 ! orce refresh
0170 IF x'sort=col THEN LET x'sort=0-col ELSE LET x'sort=col
0180 LET x'colno.row.backcolour.$=STR(col)+SEP+STR(row)+SEP+"Default"+SEP
0190 WEND
905
ODBC / Re: Extract on ODBC Sql Server
« on: August 22, 2018, 02:58:23 PM »
What are your [ODBC] configuration settings in the system INI file and what options do you have in the OPEN for the connection?
906
Thin Client/WindX / Re: Printing from Application Server
« on: August 22, 2018, 01:51:00 PM »
Generally you can access the local printer on a WindX session by issuing
OPEN (1) "[lcl]*winprt*"
HOWEVER -- If the user has enabled the WindX security and has not provided you access to the workstations resource you will receive an error 61 - "Authorization Failure".
By default the first time WindX starts up the user is asked if they want security enabled to which the default answer is "Yes".
When security is enabled whenever the host asks to access a local resource the user will be asked if they want to allow it to which the default response is "No -- refuse access" and will result in an error 61 on the server.
The user also has the option to make his response the default response to avoid being repeatedly asked the same question.
To reset security you should be able to press ALT-SPACE and select the "Reset WindX Authorization" option from the system menu.
OPEN (1) "[lcl]*winprt*"
HOWEVER -- If the user has enabled the WindX security and has not provided you access to the workstations resource you will receive an error 61 - "Authorization Failure".
By default the first time WindX starts up the user is asked if they want security enabled to which the default answer is "Yes".
When security is enabled whenever the host asks to access a local resource the user will be asked if they want to allow it to which the default response is "No -- refuse access" and will result in an error 61 on the server.
The user also has the option to make his response the default response to avoid being repeatedly asked the same question.
To reset security you should be able to press ALT-SPACE and select the "Reset WindX Authorization" option from the system menu.
907
Registration and Setup / Re: Windx Security
« on: August 20, 2018, 04:11:53 PM »
You should be able to click on the title bar icon or press ALT-SPACE then select Reset WindX Security which should bring up a message box to enable/disable security.
If this is not working try removing the file windxcfg.ini in C:\Users\<user name>\AppData\Roaming\PxPlus and restarting WindX.
If this is not working try removing the file windxcfg.ini in C:\Users\<user name>\AppData\Roaming\PxPlus and restarting WindX.
908
Wish List / Re: modernize the documentation
« on: August 17, 2018, 09:27:35 AM »
As a follow up Devons comment, the examples in the POS function are prefixed by a statement:
Given A$="The quick brown fox":
Based on this being the case and A$ has the specified value, the examples of the function formats and what they will return are all correct.
Your trainee likely missed the fact that A$ had to have a value which is why they misunderstood the examples.
As for the the examples not being complete/functional statements, the assumption is that the reader has a basic understanding of what a function is and how should be used.
Lastly, your earlier comment about GOTO is inappropriate given that most PxPlus applications have come from older programs where GOTO was generally used extensively. Given that often documentation is used by trainee programmers (as you mentioned), these individuals need to understand the use of the GOTO directive if they hope to maintain older applications. Not providing examples using GOTO would leave these trainees at a disadvantage, much as not including text mode directives such as INPUT or ACCEPT given newer application are primarily graphical. The that point, even not showing the use of line numbers, would also be problem for new hires attempting to learn the environment.
Not every PxPlus application is fully graphical using structured programming techniques without line numbers or GOTOs.
Given A$="The quick brown fox":
Based on this being the case and A$ has the specified value, the examples of the function formats and what they will return are all correct.
Your trainee likely missed the fact that A$ had to have a value which is why they misunderstood the examples.
As for the the examples not being complete/functional statements, the assumption is that the reader has a basic understanding of what a function is and how should be used.
Lastly, your earlier comment about GOTO is inappropriate given that most PxPlus applications have come from older programs where GOTO was generally used extensively. Given that often documentation is used by trainee programmers (as you mentioned), these individuals need to understand the use of the GOTO directive if they hope to maintain older applications. Not providing examples using GOTO would leave these trainees at a disadvantage, much as not including text mode directives such as INPUT or ACCEPT given newer application are primarily graphical. The that point, even not showing the use of line numbers, would also be problem for new hires attempting to learn the environment.
Not every PxPlus application is fully graphical using structured programming techniques without line numbers or GOTOs.
909
Programming / Re: Catching a tab into a grid
« on: August 16, 2018, 10:48:49 AM »
If you have signal all changes (auto mode) then the system will treat each cell as if they were their own control thus if you have On focus events being signaled then you will get a signal when entering any cell regardless of how you got there. If you don't have Signal all changes then you will only get a on focus event when the grid itself is entered regardless of which cell.
There is no real way to determine if the focus but there is a kludge that might get you want you want.
In the Onfocus event for the grid check the value in MSE(25,2) which should have the binary value of the last control with focus. If it is not the Grid's CTL id then you can from an external control however you will need to force a reset of this value by then issuing a SET_FOCUS 0. Nomads when it finds focus is on 0 (the window itself) will force focus back to the Grid so when you next check MSE(25,2) the last control to lose focus will now be the grid itself.
Something like this:
x=dec(mid(mse,25,2)); if x<>id then set_focus 0 else (change of cell focus event)
As I said -- its a kludge but might provide what you need.
There is no real way to determine if the focus but there is a kludge that might get you want you want.
In the Onfocus event for the grid check the value in MSE(25,2) which should have the binary value of the last control with focus. If it is not the Grid's CTL id then you can from an external control however you will need to force a reset of this value by then issuing a SET_FOCUS 0. Nomads when it finds focus is on 0 (the window itself) will force focus back to the Grid so when you next check MSE(25,2) the last control to lose focus will now be the grid itself.
Something like this:
x=dec(mid(mse,25,2)); if x<>id then set_focus 0 else (change of cell focus event)
As I said -- its a kludge but might provide what you need.
910
Language / Re: html character translation from forum to outlook
« on: August 15, 2018, 10:38:46 PM »
Mike, the problem is with Outlook so it would have to be fixed by Microsoft. What we send is correct and works on other versions of Outlook and other products.
BTW If you look at the last entry on the link I sent it indicates the same happens with the 32bit version.
BTW If you look at the last entry on the link I sent it indicates the same happens with the 32bit version.
911
Language / Re: 12.50 PxPlus on Server Changes to 12.51???
« on: August 15, 2018, 01:43:57 PM »
The version numbers on the server should not be changing unless there was an update of some kind.
The system checks when running Nomads to make sure that the WindX version is at least equal to the host version to avoid the system generating commands to WindX that it does not understand. Now technically 12.51 is unlikely to generate anything 12.50 cannot handle but its a generic check for version numbers.
You can likely just remove it temporarily by editing *obj/nomads.pvc.
The system checks when running Nomads to make sure that the WindX version is at least equal to the host version to avoid the system generating commands to WindX that it does not understand. Now technically 12.51 is unlikely to generate anything 12.50 cannot handle but its a generic check for version numbers.
You can likely just remove it temporarily by editing *obj/nomads.pvc.
912
Wish List / ODBC Access to Passworded Files
« on: August 14, 2018, 03:42:25 PM »
PxPlus native files can have passwords assigned to them to prevent unauthorized access and provide data encryption. The ODBC driver however does not support any mechanism to supply file passwords thus the ODBC driver was not able to grant access to these files.
For PxPlus 2019 we have enhanced the native file encryption to include the ability to use the industry standard AES encryption algorithm so that more sensitive information such as credit cards numbers and personal data can easily and safely be included in your native files.
This however brings up the question as to whether we should provide access via ODBC and how this can be done.
Before we start looking into methods to provide this capability we would like to know if anybody would use this feature so we may plan accordingly.
For PxPlus 2019 we have enhanced the native file encryption to include the ability to use the industry standard AES encryption algorithm so that more sensitive information such as credit cards numbers and personal data can easily and safely be included in your native files.
This however brings up the question as to whether we should provide access via ODBC and how this can be done.
Before we start looking into methods to provide this capability we would like to know if anybody would use this feature so we may plan accordingly.
913
Programming / Re: Very Slow Input Handler Program
« on: August 13, 2018, 12:18:03 PM »
Lawrence, I have changed the subject line for this topic to better indicate that your performance issue wasn't program Load times, but rather poor performance in your input handler when running under WindX.
When running under WindX, all FIN/FIB/MSE requests get forwarded to the workstation for processing as some of the information returned is only know at the workstation such as window handle, position, etc.. It is therefore important to minimize the number of these types of requests since on a slow network they can adversely impact overall performance.
It should also be pointed out, if you are using these function to get/save information about the device (so that your program can change settings then restore them) you would be better served by switching to the 'SA' and 'RA' mnemonics which save and restore terminal attributes.
When running under WindX, all FIN/FIB/MSE requests get forwarded to the workstation for processing as some of the information returned is only know at the workstation such as window handle, position, etc.. It is therefore important to minimize the number of these types of requests since on a slow network they can adversely impact overall performance.
It should also be pointed out, if you are using these function to get/save information about the device (so that your program can change settings then restore them) you would be better served by switching to the 'SA' and 'RA' mnemonics which save and restore terminal attributes.
914
Programming / Re: Very Slow Program LOAD
« on: August 10, 2018, 11:45:27 AM »
Lawrence, if a single FIN request is taking a long time to return then your network is slow. This is either due to the line speeds (bandwidth), too much traffic, or latency. If using satellite communications latency delay is generally over 600ms per packet caused mostly by the time for the transmission to get bounced off the satellite regardless of bandwidth.
I suggest you time the turnaround for functions like FIN and if these are not less 200 ms (1/5th of a second) then I would strongly suggest you not attempt to use the network for anything but text mode communications. Trying to run a graphical environment such as WindX with slow packet delivery is not likely going to yield an acceptable results.
I suggest you time the turnaround for functions like FIN and if these are not less 200 ms (1/5th of a second) then I would strongly suggest you not attempt to use the network for anything but text mode communications. Trying to run a graphical environment such as WindX with slow packet delivery is not likely going to yield an acceptable results.
915
Nomads / Re: Logic with Numeric Multi_lines
« on: August 10, 2018, 10:02:05 AM »
If the control is set as number then use the numeric variable.