>I have a form that is used for each users timesheet entries. The problem that I have though is that each user has their own DBF. (i.e. \DATA\THSHT\%user name%\TMSHT.DBF). Each user can only access their own TMSHT.DBF. My question is this. I don't know which DBF needs to be opened until the form is run so what is the best way to handle this in the DE of the form?

Is there a reason for this design instead of having one table for all users? What you are attempting is sort of a distorted normalization, but doing it by the book might avoid these problems. The way I track this stuff is with two tables: one user data table with basic user info (username, password, priveleges setup date, etc) and one with login history for all members (member_id, activity name, datetime). There is really no need for separate tables, unless of course there are some file privelege issues or other special security considerations. HTH