Thomas

Note that a numeric defined in the PxPlus data dictionary with a length of "10" will be assumed to have no decimals.  You should have defined it in the PxPlus data dictionary as 10.2 or similar.

If you don't specify any decimals in the PxPlus data dictionary then our ODBC interface will also report no decimal which could cause trouble for other programs.

Applications for Windows can come in 32 bit or 64 bit varieties.  Some come in 32 bit only, some in 64 bit only and some both.  While most Windows systems now run the 64 BIT OS, a large number of Windows programs are 32 bit.  Generally if there is no need for more than 2GB of memory in an application 32 bit is all that is needed and will generally take up less memory to run.

PxPlus currently only ships a 32 but version for Windows but 32 and 64 bit versions for most Linux systems.

As for installing the MySql library, how you obtain the 32 Bit DLL is really up to MySql as I do not think we can legally ship it with PxPlus as its owned by ORACLE.

So just write the data with a sequence number as in:

OPEN (1) "*memory*;keydef=[1:1:4:B],[2:1:10:C]"
WRITE (1) 1, "Dog"
WRITE (1) 2, "Cat"
WRITE (1) 3, "Pig"
WRITE (1) 4, "Ant"
WRITE (1) 5, "Pig"
WRITE (1) 6, "Zebra"

Now you can access by number (primary key) or by name (kno=1) plus you could add additional columns to the record if required.  You can access this as follows:

->print rcd(1,key=4)
4
Ant

->print rcd(1,key="pig",kno=1)
3
Pig

->

The issue would not be so much on the FIND but a potential issue if you had keys of "Mike", "MIKE" and "mike" -- which would the FIND return?

What you could do is spin through the array using the DIM(KEY array[index] ) to get the keys or use the FOR directive to walk through the elements as in:

0010 LET x$["John"]="Smith"
0020 LET x$["john"]="Jones"
0030 FOR n$ INDEX x${ALL}
0040 PRINT n$
0050 NEXT


While not a PDF the Windows download includes the full manual in CHM format.

Generally there is no guaranteed way to trap the closure of a web browser and certainly no way for PxPlus to handle or even be notified about it without you putting some code (JavaScript) in your web page to handle the issue.

Most browsers support an 'onbeforeunload' event where you can display a warning message if that is what you want.
You can also try trapping the 'onunload' event and have it send a Ajax style message to the server -- however at this point you cannot prevent the closure from happening.

Regardless of what you do you need to consider that the browser being closed may be due to circumstances beyond the control of the user or browser.  Power failure, reboot, forced close, loss of connection, etc.. are all reasons that your browser connection may be terminated.

What I would suggest is you create some form of background polling between the browser and PxPlus where you can consider no polls for a period of time as a disconnect.  This s what iNomads does in order to help assure the browser is still connected as well as setting an 'onbeforeunload' event handler.

As a side note, if you are looking to trap the browser closure so that you can 'save' information the user has entered you might consider using 'localStorage'.  You could create some JavaScript to preserve user input, form information and state in Local storage. You could re-use this later when the browser was restarted and the user re-connected to the site.  Perhaps by attaching to the onsubmit event you could save the data being submitted and target URL, then on reconnect re-submit the data.  Good web logic should already be capable of handling re-submissions so you likely would have little to change on the host and merely have to create some JavaScript to attach to the <form>.

Just an FYI -- I just added this to be addressed with the next release.