Cedric

Glad to have been of assistance ... guess my little grey cells are still of some use.  Hercule Poirot would be pleased. 

If you want URL encoded with UTF-8 then use NATIVE:URL as in the following

->x$=$E9$
->utf8$=cvs(x$,"ASCII:UTF8")
->print cvs(utf8$,"NATIVE:URL")
%C3%A9


Have you tried CVS(string$, "ASCII:UTF8") to convert the data to UTF8?

If you need it HTML encoded, once you have the UTF8 string you can convert it to HTML using CVS(utf8data$, "NATIVE:HTML"); however this will yield é    (You can also use "ASCII:HTML")

->x$="This is test "+$e9$
->utf8$=cvs(x$,"ASCII:UTF8")
->print cvs(utf8$,"NATIVE:HTML")
This is test é

Another possibility might be traffic related.  The system only provides a limited time for the SSL/TLS handshake to complete so if the host server is slow to respond you might get a connection failure.  The connection timeout is there in case you accidentally connect to a non-secure server which is not going to respond to the connection request.

Unfortunately I don't remember what the default timeout value is nor if it is able to be changed.

I would suggest if the error is "failure to connect" you simply retry the request,

Regarding precision, internally numbers are saved as 64 Bit (4 x 16 bit) integers with a precision providing 18 digits.  Older versions only had 48 bits (3 x 16) which only supported 14 digits. The current documentation should refer to 18 digits.

When Pxplus/Providex was originally developed hardware didn't directly support 64 bit math operations thus as hardware matured the language was able to support higher precisions.

PxPlus contains a built-in option to compile programs from text files using the -cpl command line option.

Check out:
https://manual.pvxplus.com/?PxPlus%20Installation%20and%20Configuration/Launching%20PxPlus/Overview.htm#cpl

Using this, you may be able to integrate the compiler components into VS Code.

When you say SELECTED do you mean the rows of the grid whose check box is checked?

If so the best solution would be to read the whole grid into a single string using GRID FIND ctlno,0,0,string$.  You can then parse the string row by row (delimited by $0a$), and extract the last column (delimited by SEP).  This will allow you to find which rows to process.

To reset all the check boxes us a GRID WRITE ctlno, lastcolno, 0, ""
... where lastcolno is the column with the check box.

You should be able to create a small web page that could provide this functionality for use with Webster+ or other Web based PxPlus applications.  There is a SpeechRecognition API within most browsers that can be used to provide this functionality as long as the user/browser is online. 

Most browsers (like Chrome) forward the data to a central server for processing so you would have to consider the security and potential sensitive nature of the text you are transcribing.

NOTE: Unfortunately the *browser interface within PxPlus does not appear to allow access the to microphone so it would only work with a stand alone browser such as Chrome or Firefox.

I have used a Linux SVN server with the PxPlus interface for years.  Basically you setup the SVN server on the Linux box and establish/save a SSH connection using putty.

Once this is done you can use the url of svn+ssh://puttySaveName/..directory.. in TortoiseSVN to browse/access the repository providing access to your Linux SVN server from Windows workstations.

Most routers will provide a port forwarding option which will allow you to forward a request from the internet for a specific port to be forwarded to an specific workstation behind the router.

You indicated that the workstation running ezWeb is running on the internal IP 10.0.0.71 port 8080.  Given this set your internet router to forward incoming requests for port 8080 to that internal IP 10.0.0.71 port 8080.  You should then be able to access your application using http://72.50.4.97:8080/inomads

If desired you can use the router to change the port number.  For example if you want set port forwarding of port 80 to port 8080 thereby eliminating the need for the external URL to include a port number since HTTP by default implies port 80.

Now if your router is connected to the Internet and it IP address is dynamic (that is your provider can and does periodically change the IP address) you might want to consider using a dynamic DNS service so that rather than using the IP address people can use a name to access your application.  Personally I have used freedns.afraid.org for a few years and it has worked well.

Assuming this is all set correctly you should be able to access your application.  If you are having trouble its possible your workstation's firewall might be preventing external access.  Try disabling the workstation firewall temporarily and see if that solves the problem.  Many firewalls have settings that allow local access through the firewall but prevent external network access.  If disabling the firewall works then check your firewall to make sure it allows public incoming access to port 8080.

PxPlus only had JSON support as of version 11.  Version 9 is from 2010.

Just checked and it appears smtp.office365.com does claim to support standard SSL connections on port 465. Using this port should allow you to simply use a initial SSL/TLS connection avoiding the need to issue STARTTLS.

Why wouldn't you simply use the standard mail interfaces included with PxPlus.  Simply convert your existing home-grown interface to call the standard interface so your application code remains the same for the most part?

Phil

You can use the img tag in webster, however the image source will need to be directly accessible through the Internet.  This is likely something you won't want.  For example if the image had sensitive information such as a payroll stub or invoice with pricing you would not want to have the images directly accessible.

Using the [picture] shortcake allows you to display any image (or pdf) from any directory as long as the requesting browser is signed on to the system with appropriate security.  This is done by encrypting the full pathname of the file being requested within the src= used by the img tag generated by the [picture] shortcake.  This renders the value in the src= useless by anybody other than the desired end user whose encryption key is maintained by Webster.


Mike

Phil

Actually the picture short code is designed to make it easier and more secure to display images. 

Basically you can have the system show a picture from any location/directory as the system will generate code that encrypts the pathname forcing user security to be applied.  This means you don't have to place images (which could contain sensitive information) on a directory that can be directly accessed via URL.  The encrypted pathname is based on a key that is specific the user making the request therefore providing additional security.