Sage 100

What's the best way to clear the Activity Log? I have a client that uses VI extensively and after three years, the log takes so long to load, it's unusable. Not sure what bonehead decided that every record of a VI import had to be recorded here.

Just rename it. I think a new one is created when one doesn't exist.

Is there any harm in just renaming the MAS90\MAS_System\SY_ActivityLog.M4T?

I may have to stop the service before I can rename it. Thanks for the tip!

I never access that because it is too slow. I always create a Crystal Report, and put in a date range, filter out user logins, and anything else I don't want to show up on the report (eg VI jobs).

That log is of marginal use and over the years has never changed. Sage could put so much more into it that would be valuable from an audit and control nature. Have any of the developers improved on this with their own audit log?

I think DSD has a login and logout modification ( http://www.dsdinc.com/enhancement/lm-1031-user-login-activity-log/ ) that I've used once for a banking customer. However you are right - I do receive quests from users about whether the capability to capture login and logout activity is available. This is usually something the auditors ask. I think if you have unified login turned on then you may get an indication of login/logout. How little coding would it take to make this type of minor change?

@WayneSchulz so true. Yet another instance of missed opportunity to demonstrate attention to enhancing the product. But, hey, we now have a reasonably sized AP invoice field so what more could we ask for the

I agree that the activity log needs work. They need to be careful as to what is included... Too many writes to the activity log can degrade performance and we complain .. Too few and we complain....

Well, I've never understood the need to capture VI job details since the log exists in VI itself.

@AlnoorCassim provide some background on the activity log a while back... https://90minds-com.socialcast.com/groups/18798-sage100routine

@MoiraGoggin - Can you repost the link to Alnoor's background. I think your link is missing some critical information. My searches are goose eggs.

@JeffSchwenk - sorry I'll need to learn how to copy those links again, in the mean time here's the particulars posted by @AlnoorCassim in 2012: Very glad Crystal (ODBC) worked out for you. That was my 1st preference too. The story behind it is it first start getting bloated up in version 4.0x where everything was getting written to the log. I must've had 20 cases of this to deal with. Also the way they designed it was a listbox that gets every single record loaded in there before you can see anything. If you were just able to hit Print to interrupt it while loading to bring up Activity Log Report, you could preview it much faster that way. Then in 4.10+ they reduced some of the repetitive places where log got written to and this problem wasn't as prevalent. But then when PCI / PA-DSS updates came out for 4.3 and 4.4, since then many more events got written again for compliance reasons and old problem happening again but not as bad I think. You're right that in there's never been any design changes to the Activity Log in terms of archiving or purging or even searching (try doing text searches on the Description field). I always have to dump it to Crystal and search.There's a probably an enhancement request already on the V1 site.

@MoiraGoggin - Click on the date/time of the original post. That will open the thread in a separate browser window from which you can copy the URL link.....

AHA!!!! Thank you @JeffSchwenk!!!