Its not that I don't want to store data in a table. The reason I can't do that for this problem is that we're using SQL shared tables and there's multiple users on the application. I need a way to test each individual user at log on time to see if they logged on thru the correct path. If they did, I need a way to indicate that so if they don't the next morning, they will get an error message. Using a shared table to store a 1 or 0 for what an individual user did doesn't work. Unless of course, I created a record for each user in the table. And that is an option, but we're on a big production server and making a new table(s) and R/W sp's, etc. is a little more than we'd like to do for this situation, especially since I think I found a way to solve the problem using a tiny form. That form stays with our production version; when our user's sign into the application, we actually COPY that production version to the indivdiual's drive on our server. That way, he/she is using their own copy of the app. Once the user opens the main form, the little hidden form that got copied over with the proudction version is deleted. Now, if the next morning, that same user logs on to the app by going directly to his individual drive on the server, code behind the main form will look for that form and it won't be there - cause it was deleted the day before. An error message will then tell the user to log on correctly, etc. etc. Bottom line is each user will have to user our procedures to copy the production version or they won't be able to log on.
I'm sure this is way more than you needed to know, but typing it all out like this sort of clearifies the logic in my own mind.
Thanks again.