>>Since we log into the UT using an ID and password, it should be quite easy for the UT to figure out for itself how often we access it. It's a program, and it knows our accounts, as well as what day it is. It doesn't need our help.
>
>I did that once with one of my apps to study usage, you need a separate table to write all the login data to, it's no big deal to set up...
>
>So, then I had this table with all the users that logged in for some period, with number of logins. In the end, it turned out to be quite meaningless, just as this survey may be, depending upon the goal - because I forgot to keep track of time in app. That's an important consideration if trying to gauge usage.
>
>IOW, some users left it on all day or even multiple days, others logged in/out many times per day. If all you want is how many logins, fine, but for usage, it doesn't mean a lot without time-logged-on data. And even that may not mean much, since some users leave it open without using it for extended periods...

There's still a way around it. If people keep it loaded, the program can still track their message submissions, or display requests.

Based on their login date, and the time of day, the program could surmise that they are using it several times per day. That would be an implied multiple login for the day, rather a one-time, hour or less, login period.

Plus, if there is one login that lasts more than a day, and there is still activity on the account, then it could mark it as 'everyday'. Otherwise, the next login will start the whole process again. There is no need for interactivity in this case.

---Michael