If you are concerned about sharing of the DBC, you can store a copy for each user int heir home directory, or in the drive/directory pointed to by the ROOTDRIVE setting. Again, this will allow you to use a common path in the code yet each user will have their own file. For example, if a ROOTDRIVE setting is made on the server using the W: drive, you an create a W:\myapp directory and copy the dbc there. In your code, you could then refer to the dbc as W:\myapp\mydbc. This would work for each user, even though for each user, it's not the same file.
If you run into contention problems storing the DBC on a common network drive, then you would have the same issues using a common DBC in a Citrix environment. I would guess you could run a higher user load then int he network case, simly because you would be dealing with native file system locking and not a network redirector's locking, but eventually the same issues would be raised. Better safe then sorry.
I don't see this being a problem, and I don't think your Citrix administrators would have a problem with it, either. Most apllications have certain settings and files that must be stored on a per-user basis, even if the bulk of it is common for all, so what you propose is nothing out of the ordinary.

Randy

>Hi Randy,
>
>Thanks for the reply. We use views and install the DBC on the workstation to avoid locking conflicts. But in a Citrix environment, we may still have problems if multiple users are trying to share the DBC. We will probably recommend that each user have his own directory containing what would be on the workstation in a typical LAN environment. We already have built-in routines to keep the workstations updated. Do you think this will cause any problems? It sounds like Citrix administrators are used to dealing with these types of issues. I suppose if they want to save disk space, they can copy common files out to a separate directory, as long as they understand that certain files shouldn't be shared.
>