6.0 ability to assign a different auto process table

[Richard Kreiss]

Apparently there is a bug in the Windows Only version of 6.0.02.14 that does not allow the use of Auto-processname or anything with Auto as the start of the alternate auto process name as this will cause an error.

I usually use a{process name or auto_process{name to quickly identify a process that is used as an alternate auto process.  This makes it easy to insure that the correct auto process is used on the command line.  Keep in mind that the -y option is not necessary when the alternate auto process is selected and the time the tok process is created. Just make sure that that the proper processing is selected or else filePro will look to the auto.prc(Windows) or prc.auto(*nix Systems) processing when the process is used.  Also keep in mind that that this option should not be selected id the processing table will be used with different auto process at run time when the -y command line option is used to use the auto process for that application.

Fp support checked this on their *nix system but it appears that this is a Windows only issue that will be corrected in the next maintenance release.  For those Windows developers, remember to report any issues you are having as *nix users may not be having the same issue and vice-versa. Issues can  not be corrected when they aren't reported.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: winmail.dat
Type: application/ms-tnef
Size: 14789 bytes
Desc: not available
URL: <http://mailman.celestial.com/pipermail/filepro-list/attachments/20210212/afe01e43/attachment.bin>