I noticed this issue while running 3.06. I started running 3.06 about 8p local. I run ANRB 24/7. All seemed well when I went to sleep night. This morning, I checked my scheduled reports that run around midnight keeping an eye out for anything unusual in the log data. I did find something odd. According to my custom report that runs against MyLog.db3, there were no flights logged after 10p local. However, as I looked at screen in the morning all looked fine. I also checked ‘my log’ from within the application and the grid showed that had I indeed logged flights since 10p and into the morning.
So, I did a little more checking. I looked at the log file details using file explorer to see the last access times of MyLog.db3. MyLog.db3 showed a last accessed of approx 10p. I then noticed that my MyLog.db3-joural file was being updated in real time and was up to 1mb in size. Normally the journal file is a few kb or 0 in size. ( My assumption is that the journal file contains the latest db transactions and is emptied after they are written to MyLog.db3.). Well, I did a File->Exit and then restarted. I checked the last access time of Mylog.db3 and it corresponded to the start time of the application. I made a copy of MyLog.db3 and ran my report query using SQL Maestro. All the data in the journal file had been written to MyLog.db3.
I have been keeping an eye on the db files when I can today and it seems that the journal starts to grow approx an hour or two after restarting ANRB. I did not see this taking place in earlier versions. I have been running 3.02 since its release prior to the 3.06 version.
Anyone else notice this? (Although, it is a bit hard to detect unless you are looking for it)
Sorry for the long Post
--Steve in Southern California.
------------------------------------------
Processor : AMD Athlon 64 3200+ @ 2000 MHz
Physical Memory : 4096 MB (4 x 1024 DDR2-SDRAM )
Video Card : Nvidia Corp GeForce 6150 LE
Hard Disk : WDC (640 GB)
Operating System : Microsoft Windows XP Professional Service Pack 3