We have this under review however the challenge is that the original design permitted only 1000 controls for a panel and these were split into 200 for the main panel and 200 each for up to four concurrent panels.

What we are considering is allowing the main panel to have more but reducing the number of concurrent panels.

In the interim what might work for you is to maximize the main window and create four concurrent panels on top of the main window.  Set the concurrent windows as frame-less and synchro-lock.  This would get you up to 800 controls (1000 if you put some controls on the main window).

Other options to get beyond 200 items on the screen are:

• Use Radio buttons for Buttons and in the select logic use the ID to determine which actual button was pressed and then reset that button so it looks normal.  This will get you 255 buttons per radio button. With a little effort you can replace up to 255 buttons, check_boxes or radio_buttons with a single control.  (We use this technique in the Bitmap selector for the Nomads designer)
• Use a GRID where possible and hide the grid lines and column/row headers while setting the background to the same as your screen.  This can get you input fields, drop down lists, buttons, and check-boxes along with variable text.

When running PxPlus on Linux/AIX or similar systems, the system will load the SSL libraries when the first reference is made to any component within the libraries is required.  The fact that the SSL libraries are not directly linked into the EXE allows these libraries to be independently updated.  The same is true for Windows however there we actually ship current SSL libraries with the product as opposed to relying on the OS supplying them.

Not all applications will need the SSL libraries, but the following PxPlus functions do require them to be present:

• Any access to SSL/TLS communications (TCP, HTTPS, etc connections)
• Use of the HSH functions other than the basic hashing algorithm (hash type 0)

Over time the SSL libraries on your system may need to be updated to address problems and deficiencies that may be discovered and corrected by the makers of openssl.   On Linux and most Unix based systems, these updates can be obtained using the OS supplied software update utilities.  For PxPlus for Windows, these can be extracted from newer versions of PxPlus and applied as needed.

Because security is so important we kept these libraries external from PxPlus so they may be updated as needed without having to replace/updated the whole PxPlus installation.

Harry, while I have in the past advised people of ways to accomplish this, I suspect many felt it too complex so I decided that I'd post a solution myself.

Basically my solution is to create a unique file/table reference based on the columns you want to select so that the data being returned only consisted of the fields you wanted. 

There is a fairly easy way to accomplish this using some of the build-in functionality within PxPlus.

The Scenario:

Lets assume you want to have you application be able to run with native files or SQL tables interchangeably and you have a file called "PRODUCTS" which has a variety of columns including a primary key of the PRODCD$, a NAME$ column and a PRICE column.  In order for most of your code to be compatible  when running on a SQL based table, you have a PREFIX FILE which defines type of database, database name, table name, etc. so that in your code you only ever have to issue an OPEN to "PRODUCTS"

Now you want to create a PxPlus SELECT that will work on either type of file but to improve database access speed you only want the system to pull the PRODCD$, NAME$, and PRICE columns down from the server.

The Solution:

To make this simple to use from your code, create a dummy system library link file called *fields* which points to temporary memory file but invokes a device driver (*dev/fields) to actually return the data you want.

So here is the device driver which you need to save in *dev/fields:

! Field Field filter driver *dev/fields
 !
  file_chn=lfo
  read data from fin(lfo,"FILENAME"),sep=";" to *,filename$,fields$,keyno
  if filename$="" \
   then end
 !
  close (lfo)
 !
  open input (file_chn,iol=*)filename$
 !
  file_type$=mid(fib(file_chn),19,1)
  if file_type$="2" or file_type$="K" \
   then goto Keyed_file
 !
  if pos(file_type$="OoQa")=0 \
   then msgbox "File "+filename$+" not a valid type for Filter";
        close (lfo);
        exit 10
 !
 ! Database file
 !
  p$=stp(pth(lfo),1,";")+";**;"+stp(opt(lfo),1,";")+";"
  close (lfo)
 !
  nopts=pos(";"=p$,1,0)
  dim o$[1:nopts]
  read data from p$,sep=";" to o${all}
 !
  path$=""
  opt$=""
 !
  for opt=1 to nopts
  o1$=stp(lcs(o$[opt]),2) ! Strip leading/trailing spaces and make lcs
  if o1$="**" \
   then path$=mid(opt$,2);
        opt$="";
        continue
 !
  if mid(o1$,1,4)="rec=" \
   then continue ! Throw away original rec= if present
 !
  if mid(o1$,1,4)="key=" \
   then msgbox "key ... '"+o1$+"'";
        if (keyno--)<>0 \
         then continue
 !
  opt$+=";"+o$[opt]
  next
 !
  opt$+=";rec="+sub(fields$,"$","")
 !
  open input (lfo,iol=*,opt=opt$(2))path$
  end
 !
 Keyed_file:
  setdev (lfo) program pgn
  setdev (lfo)iol=cpl("IOLIST "+fields$)
 !
  if keyno<>0 \
   then extract (lfo,key="",kno=keyno,dom=*next)* ! Position file
  end
 !
 Post_read:
  local _ACCESS_MODE,_KEY$,_INDEX,_VALUE$,_FLAG,_KNO
  enter _ACCESS_MODE,_KEY$,_INDEX,_VALUE$,_FLAG,_KNO
 !
  local iol=iol(lfa:*) ! Preserver all values
  read data from _value$ to iol=iol(lfa:*)
  return rec(iol(lfa))

Now can run "*UCL" to define the link file in the system library called *fields* which points to *memory* as a file with the device driver above.

'Link' files utility
Name of 'Link' file?*fields*

File '*fields*' does not exist. Create?
Yes No Quit

'*fields*' links to...
Name of file/device:*memory*

What type of link is '*fields*'
File Printer Device Quit

--- Select the driver fields from the list provided ---

Okay now you can use the logical file name "*fields*;filename;field1$,field2$,...; keyno" in an OPEN or SELECT statement and get just the fields you specify.

Where:

• filename
  Is the name of the file or database table defined in your prefix file
• field1$, field2$
  Is a list of the fields you want returned
• keyno
  Is the optional key number you want to use.  For Database files the fields used in the key MUST be set in the list of fields being selected.
  

So for the example mentioned above your select would be:

SELECT * FROM "*fields*;PRODUCTS;PRODCD$,NAME$,PRICE;0"
...
NEXT RECORD

Hope this gives you some ideas as to how to accomplish what you wanted.

BTW: If you use something like this just make sure you copy/create the *fields* link file and device driver to your systems library whenever getting new software releases.

Documentation on the Excel macros using DDE is no longer easily available from Microsoft.  You can find the original documentation on Excel DDE from Microsoft in a .HLP file call "MACROFUN.HLP" however, ever since Vista, Windows no longer supports this file format so the file is not of much use on newer systems.

Instead Microsoft recommends you use the COM/OLE interfaces for Excel.  You can find a lot of documentation on the methods and properties associated with this interface online.

PxPlus (like EXCEL) still supports both, DDE for older applications and COM/OLE for newer applications.

Where are you seeing this option and what version of PxPlus are you using?

I have checked back to version 9 and not seen the option "underline & characters" for buttons.  It exists for Fonted text but not for buttons.

No problem, the %inomads object includes properties/methods that can be used to access the argument list that was included with the original URL.

These include:

• %inomads'Url_Arg$(argno)
  Returns the URL argument/parameter indicated by argno. If no parameter is present at the specified argno, an Error #42 will be generated.
  
• %inomads'Url_Arg$(name$)
  Returns the value assigned to the specified URL parameter or "" if not set.
  
• %inomads'Url_Arg_Cnt
  Number of parameters found on the URL line.
  

So for your example you could set ARG_1$=%inomads'Url_Arg$("arg_1").

More information about inomads properties and methods can be found at this link

No -- its just that the 'SkipLockedCells only applies to tabbing or movement by the arrow keys.  By default the system forces focus to the first cell in a grid.  If you want to start in a different column try setting CurrentColno in the presets to the column you want to start in.

NOTE: If the program sets the current cell to a locked cell or the user clicks on a locked cell, the system will still go there.  The 'SkipLockedCells property only applies to keyboard movement.

The problem is that the mailing list is actually maintained in the original format that the emails were received in.  This poses a number of problems in addition to the obvious issue of how to identify people's names within the email.

• The text portions vary from plan text, quoted printable, base64 encoded, UTF8, and HTML.
• Emails may contain images which may include personal information.
  

In addition the email headers would need to be striped as they include personal tracking info such as IP addresses.

Even if we could somehow extract the mails and pull out/mask the identifying information, most Personal Data rules require us to allow user to be provided copies of, edit or delete the contents of any email they posted and a list of who the email was sent to. 

As we have mentioned, we are adding entries to the FAQ and Tech Tips sections of this forum as the issues come up.
There is also the issue that many of the old responses are just out of date and contain information that is no longer relevant on the newer PxPlus versions and including these cold potentially just confuse people.