The following is an example of using the vba output of CompareEM in a real world application.
I have an application I use to provide my customers insight into billings for their enterprise server computer usage. Some of these customers add more than a 100,000 rows a month to their tables, and some customers have several years on this data online. It is important for me to be able to send these customers application updates, which almost always update the schema, without breaking their existing tables.
My process for doing this is to send them a new MDE file with no tables (except switchboard). When they get the update they save it on their PC, start it up (with shift key), and do a File, Get External Data, Link Tables to link all the tables in the old application (except switchboard) into the new application. Then they open the switchboard form in the new application and the new application updates the schema on its first run.
Here's the application code to do the update, including the CompareEM generated code. Purple is my handwritten code to determine 'version' and call the update routines, Black is CompareEM generated code, and Red is changes I made to the generated code.
The only significant changes I have to make to the generated code is due to the tables being linked. Access doesn't want to make schema changes to linked tables, so I have to obtain the path to the linked tables and point to them directly. About 3 lines of code and easy to find as I have highlighted them in Red below...