PxPlus User Forum

Twitter Twitter Twitter

Recent Posts

Pages: [1] 2 3 ... 10
1
Language / Re: [EDO] V16.10
« Last post by Mike King on Today at 08:22:19 AM »
Can you confirm that your license (V14/15) is indeed authorized to access the ADO interface.  That is they are either a Professional or E-Commerce bundle or have the ADO interface package enabled.

If you were trying to use a Base licence (with no ADO add-on) then your V14 and V15 systems would not be entitled to use ADO.  Starting with PxPlus 2019 (v16) the Base license includes the ADO package along with most other add-ons. 

This would explain why your V16 WindX when connected to a V16 host would allow access to ADO whereas prior versions would not.

WindX, for its part, assumes the same package options and logical version as the host to which it is connected, thus even if you were using a V16 WindX; when connected to a V14 or V15 host you would only be authorized to use the capabilities inherent in the host version and license.

So the question is, does the host license that you are using when running V14/15 have access to ADO  (i.e. its a Pro or E-Comm bundle or has the ADO add-on)?
2
Language / Re: [EDO] V16.10
« Last post by Gilles on Today at 04:34:39 AM »
First of all, apologies :
I personally checked at the custumer's site and I found that error 61 occurs on the open and not on the write record.
So I did several tests :
v16 plugin connected to a v14 server, error 61 on the open [WDX][ADO]
v16 plugin connected to a v15 server, same error
v16 plugin connected to a v16 server, no error the request works

On my workstation, I have plugin v16 installed in C:\Pxp16

Connected to a v14 server OPEN CREATE(HFN) « [WDX]testfile » :error12
Connected to a v15 server the file is created in C:\Pxp16\windx
Connected to a v16 server the file is created in C:\Pxp16

Running a v16 plugin on a server not in v16 seems to be a problem.

Regards.
3
Language / Re: [EDO] V16.10
« Last post by Gilles on January 22, 2020, 04:38:01 PM »
Strange:

OPEN CREATE (HFN) "[WDX]T_E_S_T_F_I_L_E" result in error 12

SERIAL "[WDX]T_E_S_T_F_I_L_E"  OK
OPEN (HFN) "[WDX]T_E_S_T_F_I_L_E"
LOCK(LFO)
WRITE RECORD (LFO) "Hello world"
CLOSE (LFO)
No error
4
Language / Re: [EDO] V16.10
« Last post by Mike King on January 22, 2020, 03:57:22 PM »
It doesn't matter where the database resides, you are sending the file update request (the WRITE RECORD) to the workstation and as such using the end users security credentials to acces the database.

Because it will be using the end-user's security credentials and the access will be logged against them as a user, we need to have the user grant us permission.

You may want to verify the workstations permission settings by trying to write to any other file on the workstation such as:

OPEN CREATE (hfn) "[WDX]T_E_S_T_F_I_L_E"
WRITE RECORD (LFO) "Hello world"
CLOSE (LFO)

5
Language / Re: [EDO] V16.10
« Last post by Gilles on January 22, 2020, 03:41:14 PM »
The file is not on the Workstation.
The access is to a database on a Windows server (192.168.100.213) running MS SQL Server.
Only V16.10 has the error and C\users\user\appdata\roaming\pxplus\windxcfg.ini has
[Security]
~Enable=NO
6
Nomads / Re: Grids
« Last post by Bernie Perlman on January 22, 2020, 03:37:25 PM »
Thank you for your replies but I must be missing something very basic. I have used your suggestions and read the documentation but the grid remains as initially defined in the DISPLAY window.  I am trying to define a simple spreadsheet with columns 'Quantity', 'Price' and 'Total', each with a width of 16.  If I could ask for a few minutes of someone's time, please send me screenshots of the DISPLAY, FORMAT and PRESETS windows.  I am using PxPlus 2019. If this cannot be done through the Forum, please send to my email: bernperl3@gmail.com.
7
Language / Re: [EDO] V16.10
« Last post by Mike King on January 22, 2020, 03:16:14 PM »
As the file you are accessing is on the workstation it's likely the user who installed WindX did not give you permission to execute a local call.

Due to changes in the industry and restrictions imposed by articles such as the GDPR in Europe and similar legislation elsewhere, we now have to ask permission of the end user to allow a server to run programs locally.

The most probable cause of the error 61 you are seeing is that when the user was asked, they enabled security (the default setting) and when then asked if it was okay to run a program locally they chose no.  The user will need to reset the security settings on their workstations by pressing CTRL-SHIFT-INSERT while running WindX or selecting the "Reset WindX Authorization" option from the system menu (ALT-SPACE)

8
Language / [EDO] V16.10
« Last post by Gilles on January 22, 2020, 02:54:00 PM »
On the same Workstation we have Plugin V14.10, V15.10 and V16.10 installed.
This code runs fine in V14.10 and V15.10

1040 LET TABLE$="ZENCOURS", BASE$="C_SOCA"
1050 LET OPT$=";CONNECT='Provider=SQLOLEDB';User=SOUBAUTO;Pswd=xxxxxxxxx;DB="+BASE$
1060 LET CIBLE$="[WDX][ADO]192.168.100.213\MSSQLSAGE;"
1070 LET SELSEL$="SELECT * FROM "+TABLE$+" WHERE
COMPTE_TIERS="+"'"+STR(COMPTE:"00000000")+"'"
1080 LET RQT=UNT; OPEN (RQT,OPT=OPT$,ERR=ERREURS)CIBLE$
1090 WRITE RECORD (RQT)SELSEL$
1100 READ (RQT,ERR=ERREURS)CPT,ENCOURS$

In V16.10 we have Error #61: Authorization failure at line 1090

What's wrong?

Gilles
9
Programming / Re: Error 61 calling *winapi
« Last post by Mike King on January 22, 2020, 02:26:10 PM »
Its quite common.  Sadly due to the environment we now live in we have to err on the side of safety which means we can no longer allow remote software to access/update the user machines without their explicit consent.

As always, a few bad apples spoil everything.
10
Programming / Re: Error 61 calling *winapi
« Last post by jdegrendele on January 22, 2020, 01:49:47 PM »
Thank you Mike that's exactly what the issue was.

Jeff.
Pages: [1] 2 3 ... 10