Create your own site

Subscribe to our Newsletter


2022 CSBAstat Newsletter - 09 - Oh (Big) Brother, Where Are Thou?

Debug Logging
 
You are probably aware that CSBAstat writes out a "log" file each time that you use the application. It produces a filtered trace of what you did during your session, thus giving the CSBAstat Support Team in southern Italy some debugging clues in the event of a rare application bug. These log files are written to a folder in CSBAstat's google drive. They stick around for a few weeks and then are discarded.
 
Big Brother Logging
 
CSBAstat is also logging some events that are written to a table within the application and kept 'forever'. Each event has the date/time and a filename that is applicable to the event. Here's a summary.
 

Event

Huh? What just happened?

What's the log date/time used for?

What's the filename used for?

Backup

A copy of your MDB database was created

Knowing when YOUR  next backup should occur (as specified in your INI )

Nothing

Export

An  export occurred, containing all of the changes made by YOU  since the last time you imported

Nothing

Nothing

Import

An import occurred, containing all of changes made ALL MANAGERS since the last time you imported

Nothing

Prevents importing this file more than once

Signin

A user logged in

Your lifetime-to-date usage count is displayed on the main window

Nothing

 
Census Logging
 
You are storing counts of the number of rows in your local database. There's a count for each of the 34 tables. The counts are written to a special table called TableCensus. And like all tables that you update, it is exported (see above). 
 
With every user doing this, the Administrator can make sure that the export/import process is going well. Everyone's census counts should be the same....  
 
 
 
REMINDER: these newsletters can be found on the Welcome page of our website.