DAO.Recordset Errors after File Transfer from EAP to EAPX

[Rich Anderson]

Hi There, I recently migrated my repository to EAPX (Jet 4) using the file transfer utility.  Now, every time I attempt to add a new element to a diagram or a connection between two elements, I get the DAO.Recordset[3022] error that says the change was not successful because duplicate values would be created. I did an integrity check and it comes back clean.   So, I have reverted back to EAP, for now.       

I am using the most recent Release 14.1.

I would like to start using EAPX, if I can, but this is stopping me.  Anyone have any ideas or experience with this one?

[qwerty]

I remember this (long time ago) with a MySQL where the ODBC was misconfigured. In your case you should just send a bug report/context Sparx via mail.

q.

[Paolo F Cantoni]

Hey Rich,

After you transfer the project, you need to compact the file.  This will reset the internal counters (MSA's equivalent of sequences).  What's happening is that the counters haven't been updated to show the last record added to the DB, so when you add a new record, there's already a record with that ID.

HTH,
Paolo

[Rich Anderson]

Thanks Paolo!  That fixed it!   

[qwerty]

That's probably not an EA bug, I guess?

q.

[Paolo F Cantoni]

That's probably not an EA bug, I guess?

q.

I DID send in a defect that the final compress should be part of the project transfer functionality, but I guess that was fixed in a different timeline (binge-watching Continuum on Netflix).

Paolo

[Glassboy]

I DID send in a defect that the final compress should be part of the project transfer functionality, but I guess that was fixed in a different timeline (binge-watching Continuum on Netflix).

Highly dependent on your reference frame :-)