Daniel, That's a good theory. In fact it's exactly the one that I use for license allocation. I have two filters (one for submit and one for modify) that I have attached to our main forms. The filters increment counters in an auxiliary form and the data is logged by hour.. I use the data of our peak hours to reallocate fixed licenses.
I gave a presentation on this theory at User World last year. Dave -------------------------- [EMAIL PROTECTED] (Wireless) ----- Original Message ----- From: Action Request System discussion list(ARSList) <[email protected]> To: [email protected] <[email protected]> Sent: Thu Jul 05 01:16:13 2007 Subject: Re: Current connected users ** Hi All, The theory is use ARGetServerStatistics and run the application at an interval of 5 minutes. The result return by ARGetServerStatistics should be written in a table. The second step is to analyze data gather over, let say, a month. In my opinion discovering what users do not use a fix license even if they have a fixed license. In this manner fixed licenses can be realocated in time. Regards, Daniel ________________________________ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Heider, Stephen Sent: Wednesday, July 04, 2007 7:56 PM To: [email protected] Subject: Re: Current connected users ** ...or the API. Stephen ________________________________ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Shellman, David Sent: Wednesday, July 04, 2007 10:13 AM To: [email protected] Subject: Re: Current connected users ** Well there's always the user log also. Dave ________________________________ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of George Treisbach Sent: Wednesday, July 04, 2007 8:47 AM To: [email protected] Subject: Re: Current connected users ** "Can anybody suggest a way to get a list of connected uses to an Action Request System version 6.3? Best regards, Daniel" If you want a list you can print, create a form and create an entry with user and date/time information. Use an active link to push information whenever user opens a default form or opens 'any' form on the system. Another active link MAY be able to update the entry with log-out information when the client/mid-tier user is closed. You could also create a display form with table to list the active users. G Treisbach Harrisburg, Pa. USA __20060125_______________________This posting was submitted with HTML in it___ __20060125_______________________This posting was submitted with HTML in it___ __20060125_______________________This posting was submitted with HTML in it___ __20060125_______________________This posting was submitted with HTML in it___
