Kim,

>Almost forgot this part - the databases are recreated each year, using new data. Therefore, the dates of the dbf files change each year. This is part of why I don't understand why the system is complaining about the date. I've tried to think of every date that could be out of sync, I've wiped out the databases and recreated them to make sure that the dates would be the same on all of them, and am sort of lost as to what to do next.

When you wipe out the tables and recreate them, does "xxxx.dbf" actually get recreated, or is it possibly still using the same one?

Important question: Before you removed the programs and data from the hard drive, was it working OK? Are you sure... (did you actually use it recently before removing it?)

What is the actual contents of the "xxxx.dbf"? What is the file structure, how many records in it? Perhaps the error message you are getting is generated by the program if the OS date or DBF header update date or the contents of a field do not match with a field in some other table -- perhaps some kind of "system info" kind of table that tracks the last date the system was used?

In other words, perhaps we're assuming that we need to change the date in xxxx.dbf when it's a date in another table that would do the trick.