>I would suggest that you have a users class or add a property that holds the user name to your application object. This way you only have to access the property that holds the userid.
>
>BOb

Not a bad idea. I actually kind of do this already. I store the user's name in my class, but it isn't used after the error is finished. But, the problem I'm having is the user has just started up the system and is attempting to log in. Another user may be running a utility to rebuild indexes, which of course needs exclusive use of the tables.

I should probably store the user like you suggested though after they are successfully logged in. I'm not sure if there's a way to solve the error I get when the system starts in this case. Any ideas?