Ah - I see what you mean, Dodger. The trick is to create a user profile, a file named " .dazuser " or somesuch in the user's home directory; in it is the preferences as to where the files are found (sort of like Poser 5's ability to choose which Runtime directory you want.) That way, DAZ|Studio points to the user's specific content and perhaps a generic directory of the default models that has read-only privileges. In this case, each user can stash their own content into their own specified directories. If they want to share those, it will be up to them, and at their own legal peril, just like if I wanted to share my Runtime folder in Windows. A further protection would be to rig DAZ|Studio to create a .lock file when it starts, so that only one user at a time can run it, no matter if it's remote or local. dampeoples: Yep - and the same thing could be done on Windows 2000 Server, by firing up Terminal Services. /P