Personally I'd try fix it ASAP. To identify the files you could add the File Status and a check on open then log all files that caused a 95. If I recall correctly, using the file status and ignoring it, will probably produce the "safest" results. The reason it happens by the way is that ANSI rules were tightened between the dialects used for the 38 and 400 versions. As a result an error status (95) had to be issued to ensure ANSI compliance. I can't look it up, but this may be one of the "features" that can be disabled by a compile time option - have you checked? Jon Paris Partner400 www.Partner400.com
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.