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.

We decided it was better to split on major components since we have some clients that don't use iNomads, some don't use Nomads, etc...

We tried to keep the number of categories to a manageable level.  Having some basic sections allows users to only monitor those sections that may impact them.  Plus some boards such as "Off Topic" or "Wish List" are more suited to casual inquiry as opposed to sending email notifications.

About the only area where it might make some sense to merge sections would be "FAQ" and "Tips and Techniques"; but here too we felt the breakdown was better:

• FAQ for problems and issues people may be having or have reported.
• Tips and Techniques for ways you can improve your application you may not be aware of.
  

While similar they do serve different purposes.

First off this, based on what you sent to our support department, this appears to be an INFOR serial number thus you need to contact INFOR about what to install to run their application.

While they generally use standard PxPlus builds they have on occasion used custom builds to address certain issues they were having or to provide special functionality they may have required. INFOR can also advise and supply the WindX which works correctly with their application.

As for software activation, this too needs to be done through INFOR as they have unique activation software that not only activates PxPlus, but also their application which has its own security protection.

With regards to your activation levels, activation keys for newer versions of PxPlus will allow you run older versions of PxPlus.  The activation level on the key ONLY establishes the functionality you have been authorized to use.  Any PxPlus activation key will allow you to install and run versions of PxPlus up to the level specified in the key, and in addition you can use newer versions of the executable components (Not the library) in order to obtain fixes . 

For example a version 10 key will run any version of PxPlus up to and including version 10.  It will also allow you to run the version 11 thru 13 executables (EXE/DLL and equivalent on Linux) in order to get access to corrections. If a problem was found in the version 10 executable and was fixed in the version 11 executable, you could install/run the newer executable in order to obtain that fix.  This is valid for 3 versions which covers the product support window.  Beyond three versions you need to purchase a version upgrade(s) or be on a maintenance program.

Finally, as the serial number you reported on our help desk is from INFOR and you are having trouble, we suggest you contact them for assistance as they can provide the proper versions to install and run along with the proper activation keys.

Additional note -- your PxPlus 2017 should have a *browser control -- it came standard with PxPlus and should have been installed automatically.

Make sure your license is for PxPlus 2017 (V14).

Another option is to use *browser and pass it the page number or bookmark as in:

def object h,@(0,0,80,24)="*browser"
h'navigate2("file://c:/temp/111/test.pdf#page=5")

This works with Page numbers (#page=nnn) or Named destinations (#name).

I'm sure the information is in the core dump somewhere, but there is no easy way to locate the values.

If the issue is reproducible, then you should be able to setup the log file and replicate the failure.  If its a one time failure then it could be anything and potentially not even anything related to your application.

I would setup a log file then watch for the problem to resurface.

One simple technique for the log file is add logic like:

DayNo = JUL(0,0,0)
P$ = "/tmp/pxpluslog."+dte(DayNo +1:"%Ws")
ERASE P$,ERR=*NEXT
P$ = "/tmp/pxpluslog."+dte(DayNo :"%Ws")
SERIAL P$,ERR=*NEXT
SETDEV (0) SET "LogFile" TO P$

This will create you a daily log file with the day of the week in its name and keep the last 6 (requires the logic to run at least once per day every day). 



 

What version of PxPlus are you using also are you using the GUI or Text mode of the SplitFile routine to setup the file splitting?

BTW: An error 31 may be due to the memory limits you have set in your application.  Do you issue a START nnn to set the memory limit or take the defaults?

You may get around the problem by setting the 'SZ' system parameter to a larger number of setting 'IZ' to have the system ignore the limitation.  Note that setting IZ can cause OS problems should you have a run away process that take all OS memory.