Hello J.A.

The .LOG files are transaction logs. Everything you do in the program is done in the .LOG files and are only written to the database on Checkpoints. Nothing is stored in a log file long term, it is more of a work area during runtime.

It is perfectly normal for the .LOG file to be missing after conversion.

What happens on a copy conversion, like that of the 2015.2 update, is a new database is created, all the data from the old database is copied into the new database, once that process has completed the old .LOG and .BDB files are renamed, and in the case of the .LOG files they do not generate again until the database in opened through the client.

~Delray

It is possible that the .Log and BDB files to get out of sync, and then the database file will not open and then the LOG file would need to be deleted or renamed, but it there is no LOG file, it will generate one and continue on.

Thank you, Delray. My experience from some years ago was that FAS would not open without both .BDB and .LOG files for the same database that were saved at exactly the same date/time. I have always converted the historical files one at a time rather than using the conversion utility, and that automatically sets up a .LOG file for each database (although the historical data is sometimes kept, and sometimes not brought forward as in this case). I was able to open a converted database with no .LOG file, so this no longer seems to be an issue.