I am sorry to hear that you do not have a backup as that would be an easy fix by reverting to the database from before the issue occurred.
I am not sure what you mean by a “copy” as you are running the AyaNova configured for network Firebird Server use, and any direct access of the database will more than likely cause database corruption.
Once the Firebird Server is “serving” the database, the database file itself would never be anti-virus scaned, never be directly copied, never be moved as this will cause database issues - which may be what the issue with your database is caused by. We provide steps on how to backup the AyaNova database when using the network Firebird configuration that creates a “snapshot” of the database, and than database snapshot is what is backed up.
If ever the AyaNova database that is configured for network Firebird Server use needs to be directly moved or copied, you MUST shut down the Firebird Manager.
By direct email to email@example.com, send the following and we will go from there:
-Shut down the Firebird Manager via Control Panel on the server
-Using WinZip, zip up the AYANOVA.FDB database file
-Attach to a direct email to firstname.lastname@example.org,
-include your AyaNova Administrator username and password
-reference this Forum topic http://forum.ayanova.com/Topic3329-89-1.aspxin your email so I know what this is for
I will take a look and see what direction we go through from there.