As you are presently configured for Firebird network use, you must be careful to not corrupt the AyaNova database by moving it or copying it while anything else is accessing it.

Do the following:

1. Make sure you are out of the AyaNova program and no one else is running it.
2. Shut down Firebird Manager on the server where the AyaNova database is configured for network use right now. (Control Panel -> Firebird Manager)
3. Now that the Firebird Manager is shut down and nothing else is accessing the AyaNova database, you can now safely move/copy the AyaNova database from its networked Firebird Server location ( I believe you had C:\Data\AyaNova\). For example, move the AYANOVA.FDB back to C:\Program Files\Ground Zero Tech-Works Inc\AyaNova 3 default installation folder where you installed AyaNova to.
4. Rename your existing edited AyaNova.exe.config file that was pointing to the networked Firebird to AyaNova.exe.config.network (so that you can easily rename it back later)
5. Rename the AyaNova.exe.config.DEFAULT_EMBEDDED_VERSION file to AyaNova.exe.config
6. Now when you run the AyaNova program it will access the stand-alone database file that is back in the AyaNova program directory.
7. You can now enter in data as needed.
8. When you are ready to go back to networked, you will again ensure you are not running the AyaNova program, make sure the Firebird Manager is shut down, move the AYANOVA.FDB database file back to the that networked Firebird Server location (I believe you have C:\Data\AyaNova\), start Firebird Manager, and rename your AyaNova.exe.config.network back to AyaNova.exe.config

- Joyce

AyaNova Sales & Technical Support

http://www.ayanova.com

No, there will be no database corruption if you follow the steps in the AyaNova v3 Manual on how to convert your AyaNova firebird database to a AyaNova SQL database

- Joyce

AyaNova Sales & Technical Support

http://www.ayanova.com