Access Violation Repository Synchronisation

Yes, Unfortunately I think the end user (me) was a bit distracted and zigged instead of zagged and made it disappear. Not exactly sure how but I think I cloned, renamed and then deleted the original and then for some reason deleted the newly renamed clone. Stupid mistake. So reverting is not possible and I can see the gap in the ObjectIDs in the Object table

Recycle Bin would be a great feature

Run some tests here

1 Created backup
2 Created a brand new repository using the repository creation wizard. (SQL Server)
3 Using the repository synchronisation wizard I was able to copy objects from the backup.

However, if I do not create a brand new repository using the repository creation wizard and just connect to the empty database with no repository tables I get the AV.
So what we will do: we will add a more detailed error message

Please let me know if it is helpful or not

Let me check that. I was sure I created the repository using the wizard.

Ok. I discovered what the fault was. The backup wizard creates a .ZIP file that contains a ReadMe and a .DAT which I think is a SQLite database.

I had extracted the .DAT out and when using the Sync Wizard and indicating to do so from a Backup I had chosen the .DAT file and not the .ZIP.

So I am, guessing the AV was coming from an attempt to Decompress an already Decompressed file.

Perhaps some extra info on the file Selection dialog to have a file type of .zip as the default

Thanks

FYI We have Implemented your suggestion in the latest release.

26/05/2022 6.3.11.21

+ Improved: Repository Synchronization Wizard error handling
+ Improved: aetlcl.exe error handling