Originally Posted by
ArviLaanemets
Editing every frontend separately is not very effective, and is prone for errors happening. I myself prefer:
I have a network resource only I myself (or user group I am member of) has the access (in case users themself have to get a new copy of frontend, then they will have the reading right there too) . There are subfolders where I design new (versions) of frontends, where I archive old versions of frontends, and where I place current versions of frontends for distributing. When users have the reading rights to main folder, then they must have reading rights for distributing subfolder too, but only for this subfolder;
When I set up a new version for distibuting, all frontends for users are overwritten with the copy of this new version - so I have to design a frontend only once. The method used for distributing the new version depends on where user copies are stored (on user computer, in user's profile on Terminal Server, in network folder the user has access to, etc.), and may be either messaging users about new version to be copied, or me replacing them manually (what I dont want to do for sure!), or running e.g. windows script which does it, etc..