Hello Cedric - please provide an e-mail address and I will send you sample code and a sample Excel file to try this with.

Alternatively, you can call or mail me directly.

Hello Les:

With help from others on this forum I was able to determine how to process a Libre Calc file (.xlsx) and parse out the contents, so it is possible.

The file is actually a zip file - you can read it like a regular PxPlus keyed file. The parsing of the xml is a bit tedious but all of it is there.

Please contact me if you need some sample code. Thank you.

John Spencer
john@jdsi.ca
250 470 7521

Hello:
My guess is that the defined scroll region is not large enough for a line @ 23 - so it is wrapping to the top. I say 'guess' as I get an err 29 when I try to execute that code.
hth

Hello:

Might there ever be functionality to handle the Open Office 'Writer' and 'Calc' applications?

Thank you.

Hello Cedric:
This works for me - I hope this helps.

begin
let prog$="fillit.pvx",look$="DO_THE_FILL:",flag$=""
call "look4lbl.pvx",prog$,look$,flag$
print "Found: ",flag$

!look4lbl.pvx
enter prog$,label$,found$
!look for a label in another program
found$=""
call "*pg.cnv",err=exit,prog$,work$
let work=hfn; open (work)work$
next_rec:
read (work,end=THE_END)dat$
if pos(label$=dat$) then let found$="y"; goto THE_END
goto next_rec
THE_END:
close (work)
erase work$
!print "Found: ",found$
exit: exit

Hello:

If your account number column is defined as numeric in the list_box (ie [Column]N10)you can:

ACCOUNTS.CTL'sort = 2

after you finish loading and it will display in ascending numeric order based on column 2.

This way you can leave your data 'as-is'.

Hope this helps.

Can I supply a specific start_up program when using *windx.utl;spawn ?
Thank you.

Thank you very much Mike.

We will implement that change and see what happens.

Several times this year we have received an error 106 on a remove from a file and have reason to believe it is not hardware related as from our understanding to what an error 106 is. The file is a basic data file, external key size of 45 and defined record size of 512. The file is used during our payroll process, it has records written to it and then removed at the end of the process. The files has been in use for over 20 years in this process and I am sure has had millions and millions of records pass through it. We have not had an issue with it until this year.

Back in March of this year we had the error 106 on this file on a remove statement for the second time. At that time we ran the file rebuild utility on it. In the evening when no users were on the system, we completely removed the file from our system and defined it fresh in a different filesystem, there were no records in it at that time.

In May of this year it happened again, we took the same course of action as above.

In June we went through a system upgrade. We left the old physical hardware, upgraded to a Hyper-V virtual server, upgraded the operating system to Linux RedHat 7.6 and Pxplus v15.1

On 10/27 the error 106 returned in the same file in the same remove statement. Again, traditionally we would think this is hardware related but cannot see how that is possible based on it being the same file, having been redefined several times and now on a completely different platform.

Is there any insight that can be provided on why a file would be receiving an error 106 on a basic REMOVE (2,KEY=K$) that does not appear to be hardware related at all?

Thank you.

I tried adjusting permissions to no avail. I think a new location may be the best method to use.

Thanks Mike.

Hello:

We have used the save control 0 to bitmap.bmp on rev 10.2 - no issues.

We are now upgrading to V15 and have discovered that this no longer works. We know that the pvx.ini / pxplus.ini files can be written to by adjusting screen size/values from within the app. I am curious as to what is preventing the save control 0 from working. It currently writes to the location where Windx is installed (on V10).

I believe this has to do with new client side security in Windx but am at a loss as to how to fix it.

I can save the screens to another location ([wdx]\whatever) outside of the standard Wdx but not where they previously were saved. Thank you.

Thanks to the mas90 post below - I tried setting the terminal type to ansi, resolving this issue. Thank you.

Hello:

I am trying to migrate a Telnet Windx login over to using SSH.

I am able to connect via SSH - but not in 'GUI' mode - as the Telnet currently does.

It will only connect in character mode.

I have tried numerous times with a Link file - all to no avail.

Has anyone succeeded in logging in via SSH to a Linux machine using Windx?

Current Telnet short-cut:

"C:\PVX Plus Technologies\Windx Plugin 2018 Upd 1\pxplus.exe" ..\pvx.ini windx -arg windx_vm.cfg AUTO

with the .cfg file looking like:
TelnetŠ9600Š0Šserver.url.comŠR:ogin:Š0Š1ŠYŠ0Š0Š23ŠansiŠ0Š0Š

Thank you.