Sage 100

Sage v44 std - Getting this error at login. RDP connection. No hits on the KB

exit sage and delete the SY_ActivityLog file or at least rename it. Then come back in.

You da man!!!!!! Thanks

Why don't we have a ""utility"" to print to PDF and then purge, the Activity Log? Why, why, why... sigh.

Why doesn't Sage auto-prune the Activity Log? It's useless past a certain size anyhow

Another excellent topic of an e-mail to Deborah Nelson. This should be a ""major"" enhancement for them. Quick and easy, not much thought process involved here...

all the VI entries consume the activity log. I like sql because I can just remove those VI entries. I can also search the log and get just the errors in a view. And if it is really to big I just copy the whole table into ActivityLog2015-05 and it is still visible in SQL to see all the records.

I'd like to take this one step further. Why not have a LM setup option to include/exclude logins, VI jobs, or all except errors from being recorded in the first place?

Let us know what Deborah Nelson says...