> Borrowing an idea from someone else, you could use a table containing valid > logins. When you add a person to the login table you would create a > subdirectory (possibly matching the user's initials) and copy the default > resource file to that directory. Then when a person logs in just use the > resource file in his/her subdirectory. This way the user will always have > his/her last preferences saved and no problems with extra files if a lock > up occurs. I did that three years ago, and, moreover, put the user's resource to user's local disk. Worked just fine, and some 30 machines were added to the system without my having a slightest idea of the time it happened, never mind the place, and it worked like magic. This reminds me of another problem - for new users (it was Novell 4.01 network) I checked the existence of c:\fpd26\foxprox.esl file, and then if it didn't exist I ran a batch to create directories, copy runtime, resource files etc. The trick was that they only had to call the same batch file they would be calling ever after, and the .bat was in their path as set up from within the group's login script. Now, how do I do such a thing from Windows? They don't have the icon on their desktops; they'd still have to call some install batch. The install batch file should now probably copy a standard link+icon there, which will in turn call the app from server, and to be clever enough to find the desktop directory, and... wasn't life much easier under DOS?