Sparx Systems Forum
Enterprise Architect => General Board => Topic started by: royvanmarrewijk on June 02, 2017, 05:23:33 pm
-
Hi,
For backup and distribution we transfer our project (DBMS) to an .EAP file once in a while. Since a week or two I got the error "DAO.Field [3163] - Message to long" and the result is that the project is transfered to the .EAP but the .EAP is missing data like the tagged values of operations. The size of the .EAP is more than 1 GB and I think this has to do something with the DAO error but I don't know for sure.
So.. Do you guys know how I can solve this problem and what are the options to reduce the size of the .EAP. I already disabled and cleared the audit log and performed a Project Integrity Check.
Kind regards,
Roy
-
Probably the field sizes are different in various schemas. Look into %appdata%...sparx...DBerror.txt to see if you have some kind of indicator.
q.
-
As far as I remember 1GB is the MS Access limit (EAP-File).
What you could try is to compact you eap file. An other source of such big file sizes is enabled audit logs.
-
Do you always transfer into an empty, integrity checked EAP file? As qwerty mentioned, check the sizing of the fields. We found many inconsistencies between the various schemas. Also, STOP using an Access97 file and use an Access2000 .EAP file - that will bump you up to at least 4 GB, I think.
HTH,
Paolo