INSTRUCTIONS FOR INTEGRATING ERSYS5 WITH CLIPPER 5.0 PLLs Some users have had trouble utilizing ERSYS5 due to conflicts with the default Clipper error system which is included in their PLL. The simplest solution to this, as explained in ERSYS5.PRG, is to link without a PLL. However, some consider this requirement to be prohibitive. If you are relatively sure that you will not be making changes to ERSYS5.PRG, you may link ERSYS5 into your PLL. Below is an example of how you would link ERSYS5 into the normal Clipper "BASE50" PLL. -----------------start of BASE50.LNK-------------------------- prelink output base50 lib clipper, extend, terminal, dbfntx refer _main refer _VOPS, _VMACRO, _VDB, _VDBF, _VDBFNTX refer _VTERM, _VPICT, _VGETSYS refer _VDBG file ErSys5 ------------------end of BASE50.LNK--------------------------- If you use a different PLL, try just adding the line: file ErSys5 to the end of the .LNK file. As long as another one of your linked modules does not define "ErrorSys", this method should work. After editing your PLL's .LNK file, you then issue the following command from your PLL's directory: RTLINK @BASE50 (or whatever your PLL's name is). When you issue the above command, you must first be sure that you have cleared your RTLINKCMD environment variable of any "/PLL:" options. For example: SET RTLINKCMD= After linking, you should re-set RTLINKCMD to its former state. Or, if you'd rather not have _any_ error system (mine or Nantucket's) included in your PLL, just replace the line "file ErSys5" with the following line: exclude ErrorSys This will create your PLL without the pre-defined error system. If you have had difficulties trying to link ERSYS5 with your application, please accept my most sincere apologies for not explaining how to avoid these conflicts better in ERSYS5.PRG. If anyone still has trouble integrating ERSYS5 with their system, please feel free to contact me. Tim Palmquist 6005 Chandler Way Bakersfield CA 93307-5509 (805) 837-8730 CIS 76517,1546