When a Built Application, standalone or client-server, complains the data file is incompatible, the next step should be to run a Maintenance and Security Center (MSC) Verify against the source structure to check for any problems in the structure file.

The is because the compatibility between the Built Application and the data file depends on the UUID of the Built Application being the same as that of the source structure. The UUID of the Built Application is calculated during the build process, not simply copied from the source structure.

If there are any anomolies in the source structure that causes the Build Application process to not copy a table exactly as it is in the source structure, then the calculated UUID of the Built Application will be different. A database UUID is based strictly on the tables and fields of the structure.

Any structure anomalies revealed by a Verify in MSC should be corrected before continuing with another Build Application run. To clear any anomalies that cannot be corrected manually you should run an MSC Repair on the structure.

Any anomolies in the data file, though they too should be corrected or repaired, will not prevent the Build Application procedure from producing a clean build of a 4D Application.

If this problem still exists after MSC gives the structure a clean bill of health, 4D Tech Support should be contacted for further assistance.