Sorry. The first line should read " I have a database and an older copy of the database."

If you mean comparing field specs and properties, then each field has tons of specs: name, data type, data size, rich text or not, allow zero length or not, default value, validation rule, etc.  If you are to check for all the differences between two tables, it is not an simple job.  And you have to program everything yourself in VBA because there is no built-in tool for that.  The FMSINC website sells a compare tool for $300+ but I don't know if it's worth it for something you would likely only use once.

I just had an idea. See what you think. Suppose I  first backed up everything and then copied all the tables from one into the other. THis would give me tables such as CustomerT and CustomerT1, ProductT and ProductT1.  WOuld it then be easier to then compare once they are in the same database?

If you're talking about comparing the DATA, then you can just LINK the old database tables into your new database. No need to import them and create a second copy. But yes, then it will be easier to do a side-by-side comparison to see what data has changed.

Kevin is talking about comparing the STRUCTURE of the tables themselves (fields, properties, etc.) So... which one do you mean?

Hi Harold, unless you can check for differences with your own eyes, you are going to need VBA.  The VBA code would be of the same complexity no matter where the tables are.  I've never done this kind of thing.  Naturally it's better to avoid having to do this.  But I imagine sometimes you need to restore a backup up copy to fix problems in the current copy.