PxPlus User Forum

Twitter Twitter Twitter

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.


Messages - michaelgreer

Pages: [1] 2 3 ... 6
1
Language / TLS 1.2
« on: January 21, 2022, 01:41:37 PM »
We have some legacy customers running back at PXPlus 11.50.  This is not supporting TLS 1.2. My understanding is that PXPlus uses the dlls in the pvx directory.  I do see that this release has been modified as recently as 08/2019.  Is it possible that this was one of the areas addressed. If not is there a solution to get these versions of PXPlus to support TLS 1.2?  Will the DLLs from a later version work and would this be allowed under our license agreements?  Any help is appreciated.

2
Thin Client/WindX / Re: Using INVOKE with Windx on remote RDP users
« on: January 20, 2022, 12:30:17 PM »
Mike,

I would be suspicious of how your %LPC_COMPUTERNAME$ is being set. Assuming that you *always* want the notepad or freeware on the client PC you can detect wdx with this code: IF MID(MSE,22,1)>$00$ AND MID(MSE,22,1)<$FF$.  If this is not $00$ or $ff$ then you are on windx.  You could also test by connect from RDP and just issue your invoke with no conditional and see where the notepad launches.

Michael

3
Programming / Check for damaged files
« on: November 18, 2021, 08:10:08 AM »
Has anyone worked to incorporate *ufac into a program that will scan an entire directory and check all PVX data files therein?  I'm sure we can pull this off but wanted to check if someone else has already done this.

Thanks!

4
Language / Re: Large records in file
« on: November 02, 2021, 10:33:25 AM »
No particular reason other than it has been in place all these years.

5
Language / Re: Large records in file
« on: November 01, 2021, 03:31:23 PM »
I have successfully created this file. Now, when inserting large records via ODBC (v 5.10.0002)a 3rd party is running into this error:

 “<eb1>Expected lexical element not found: <identifier>
State: 37000; Native: 1015; Origin: [PxPlus][ODBC Driver]</eb1>”. 

Is this a limitation of the ODBC in play here?

6
Language / Re: Large records in file
« on: October 27, 2021, 03:00:52 PM »
If I nix the autoincrement can I get the extended record size?

7
Language / Re: Large records in file
« on: October 26, 2021, 05:32:17 PM »
Well now, that may be the issue. I am on 10.20. Not supported there?

8
Language / Re: Large records in file
« on: October 26, 2021, 04:48:28 PM »
Thanks Mike. Not sure I would ever have figure *that* out.  :P  Now, I just did keyed "myfile",[1:1:16:"+"],0,-30000,opt="X".  I dimmed a$(35000).  When I write to a channel with myfile opened - write(lfo)*,a$  - I get an error 1.

9
Language / Large records in file
« on: October 25, 2021, 10:50:18 AM »
I am trying to create a file with record size >32K. I am using this:
keyed "myfile",[1:1:16:"+"],0,-50000,opt="X"
This throws an error 41.  What am I mssing?

10
Language / Automation issue (OLE)
« on: August 02, 2021, 10:43:37 AM »
I am trying to duplicate this VBS script in PxPlus:

strSLXCon = "Provider=SLXOLEDB.1;Password=password;Persist Security Info=True;User ID=admin;Initial Catalog=FACTSCONNECTION;Data Source=IP-SQL;Extended Properties=PORT=1706;LOG=ON;CASEINSENSITIVEFIND=ON;AUTOINCBATCHSIZE=1;SVRCERT=;"
Set objSLXCon = CreateObject("ADODB.Connection")
objSLXCon.Open strSLXCon
Set objSLXRS = CreateObject("ADODB.Recordset")

strSQL = "slx_dbids('Account',1)"
objSLXRS.Open strSQL, objSLXCon


        objSLXRS.Movefirst
        strID = objSLXRS.Fields(0)
         objSLXRS.close

msgbox strID

Here is my code:

1000 !
1005 def object crm,"ADODB.Connection"
1007 def object rec,"ADODB.Recordset"
1010 constr$="Provider=SLXOLEDB.1;persist security info=True;Initial Catalog=FACTSCONNECTION;PASSWORD=password;user ID=admin;Data Source=IP-SQL;EXTENDED PROPERTIES=""PORT=1706;log=on;casesensitivefind=on;autoincbatchsize=1;SVRCERT="""
1015 crm'open(constr$)
1020 idsql$="slx_dbids('Account',1)"
1025 ! id$=crm'execute$(idsql$)
1030 ! print id$
1035 rec'open(idsql$,*crm)
1040 rec'movefirst()
1045 id$=rec'fields$(0)
1050 print id$
1080 drop object crm
1085 drop object rec

I do not get the same result as the VB script which does return the correct value. My code executes, but generates a completely different set of ID's.  Any pointers on what is wrong here?

11
Programming / Re: Code failure between PVX 9.1 and 15.1
« on: July 20, 2021, 11:26:22 AM »
Devon,  at the 9.1 version I get no pop up when I do the open with '!Q' set.  on the 15.1 version, on the open -same exact line of code - I get "SELECT COUNT(*) FROM".  Again, this is on an open. The code for the open is at the top of this thread.  Same DSN accessed by the 9.1 and the 15.1 version.

12
Programming / Re: Code failure between PVX 9.1 and 15.1
« on: July 20, 2021, 10:57:44 AM »
Devon, it is just on the open, but  I will do as you indicate.

13
Programming / Re: Code failure between PVX 9.1 and 15.1
« on: July 20, 2021, 08:53:49 AM »
Any word on this.  The only thing that has changed here is the PVX version.  This is a productions system and is limping along without an important feature.

14
Programming / Re: Code failure between PVX 9.1 and 15.1
« on: July 15, 2021, 04:45:31 PM »
That was stupid on my part. Sorry.  Now we are getting somewhere:

42000: [Microsoft][ODBC Microsoft Access Driver ] Syntax error in FROM Clause

Michael

15
Programming / Re: Code failure between PVX 9.1 and 15.1
« on: July 15, 2021, 04:24:49 PM »
@Mike - I had checked, but just rechecked. My Windx is 32 bit and the ODBC driver is 32 bit.  @Devon, msg(-1) is empty.  Any other ideas?

Pages: [1] 2 3 ... 6