|
midrange.com
The first "strange" thing I can see here is that the DATECTRL DB file with its
one record that "was last updated on Sunday, Nov 23rd". I guessed it should be
on or before year 2001? Maybe the good file has suffered a change in its record
layout and maybe this "bad" file version of DATECTRL is in a library that is
above the library SLK in the library list, where the good file is.
Obviously it is a level check and the system will allow the user to react at it
by cancelling the program that calls this task
("C") or to skip this error and continue processing ("I"). If this is a job
that prints reports, I guess is save to answer with "C" and verify that the file
in use in the query is the right file. You can also get in to the query itself
and exit it, by doing a "save" of it and that will help the query to recognize
the format of file DATECTRL.
Hope that helps...
Peter Vidal
Pall Aeropower Corp. / SR Programmer Analyst
www.pall.com / Peter_Vidal@Pall.com
727-539-8448, x2414
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
