Years ago, there was a product called "Data Angel", which did just this. But it never took off, why? Because in a well designed DB, it's rare to have to actually alter tables and when you do, often it involves much more than simply altering fields. Data typically needs to be transformed as well (i.e. you put in a new invoicing system, changing all the tables).
So there is no "one size" fits all type of approach.
Jim.
At the risk of being the person that always asks questions, what specifically do you mean by "detect any table or column differences between two Access databases"?
I can see several interpretations, like:
· Comparing two databases in their entirety identifying tables and columns present in one and not the other, or columns that have different schema definitions (type, scale, null, etc)
· Comparing two tables with the same name between databases looking for schema differences
· Comparing two tables with the same name between databases looking for data content differences
· . . .
»bp