Actually there is an alternative method that can be used. It's a method that utilizes a simple form that counts the number of times an individual has created or modified a record. It can be set up to create a record under hourly increments so that the data can be tied back to the peak hours.
Create a form that contains 2 integer fields and a date/time. One integer field will be used to identify the hour of the day. The other integer field is a counter field and workflow is added so that the counter is incremented on submit/modify. (I actually use 2 counter fields. One field is set up to increment on a submit and the other on modify. The ratios of submits to modifies helps me identify those individuals on the help desk and those that are doing support.) The date/time field will be set to the date and hour portion of the Create Date field. I then add a filter to our primary forms that execute a push to the Counter form on submit and modify. This simple form and workflow provides me with good data for checking license allocation. I can also determine which users are the ones using the system the most and which users have not made a modification in a specific period of time. For license allocation it's so much the number of edits that they make as that a record exists during the peak hours. The data can be looked to determine which users have a floating licenses and are making modifications during the peak hours on a regular basis. You can also look at those that have fixed licenses and are not utilizing the license during the peak hours. License allocation is an ongoing process as habits and job functions change. I only do the analysis when we near our max of floating licenses. There are times where you simply need to purchase more licenses. The data helps to make the determination if more fixed or more floating are needed. Dave -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Kern, Robert SBA Sent: Wednesday, May 16, 2007 1:53 AM To: [email protected] Subject: Re: License Monitor What we are doing over here is parsing the user.log file with Access. Works nicely so far. Yes, we don't really get how long a user has been connected, but what we can do is report a certain high load timeframe (typically when Europa and Nafta work together) and check which user has logged on at least once and get his license type. Based on that we can shift licenses to some degree. On top of that we log with a hidden form the timestamp when a user logs into the system (so we can remove the license for good if activity drops). I'm quite sure what with Misi's tool you can get most accurate data and I think it also makes the user form entry changes for you, if you want to. What I'm saying, the server statistics form is nice and we use that for getting a general overview ... for really optimizing license allocation, I can't think of any other way then checking each user (however you are going to do it). Very much like Axton says. Best greetings from Germany, Robert ________________________________ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Shellman, David Sent: Wednesday, May 16, 2007 1:46 AM To: [email protected] Subject: Re: License Monitor Yes it is a very powerful tool. I played with it last year at this time. I included a refrence to it in my presentation at User World last year. I ran data through it today. I'm making a comparison of his output against my own routines to provide some feedback to Misi. Dave -------------------------- [EMAIL PROTECTED] (Wireless) ----- Original Message ----- From: Action Request System discussion list(ARSList) ________________________________________________________________________ _______ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
