EXECUTIVE OVERVIEW: Does anyone know of any issues that could arise from
allowing multiple users to concurrently use a program file set to
automatically open "READ ONLY"?

I have a file that many users have a copy of. It contains several VBA
programs. This program file runs hidden and all programs are executed from
toolbar controls. The program file itself is static, the programs only
manipulate the file or files the users have active. The program verifies that
the correct files are open before executing any functions.

Each year a few changes are made and in the past, I have distributed this
program by e-mailing it to all users who then save their own copy locally,
with instructions to over-write their old version. This method has worked
fine for the past three years.

Here is my question. Rather than sending out a new version once a year to
each individual user, would there be any draw back or problems with changing
the program file property to always open "READ ONLY" so that the file could
be used concurrently by all the users. I could place ONE copy the file on the
network (accessible to all users). The program auto-installs a toolbar when
opened and then, as previously stated, all functions are performed only on
the user's active files.

If you have any ideas, please post back. Thanks much in advance.

I've never had any trouble with marking a file readonly (via windows
explorer???) and having several users open it.

In fact, I share several addins this way (as well as workbooks that serve as
templates).

The only problem I foresee is if the users are sometime not connected to the
network and want to use that functionality.



quartz wrote:

EXECUTIVE OVERVIEW: Does anyone know of any issues that could arise from
allowing multiple users to concurrently use a program file set to
automatically open "READ ONLY"?

I have a file that many users have a copy of. It contains several VBA
programs. This program file runs hidden and all programs are executed from
toolbar controls. The program file itself is static, the programs only
manipulate the file or files the users have active. The program verifies that
the correct files are open before executing any functions.

Each year a few changes are made and in the past, I have distributed this
program by e-mailing it to all users who then save their own copy locally,
with instructions to over-write their old version. This method has worked
fine for the past three years.

Here is my question. Rather than sending out a new version once a year to
each individual user, would there be any draw back or problems with changing
the program file property to always open "READ ONLY" so that the file could
be used concurrently by all the users. I could place ONE copy the file on the
network (accessible to all users). The program auto-installs a toolbar when
opened and then, as previously stated, all functions are performed only on
the user's active files.

If you have any ideas, please post back. Thanks much in advance.

--

Dave Peterson

I do exactly that and really have no problems. We had a very minor issue
yesterday caused by an upgrade to excel 2003 on a couple machines. On the
Excel 2003 machines the user was prompted to save the read-only, hidden file.
This was triggered by the read-only file being in an older version of excel. I
had to upgrade the read-only file to 2003. So far that has not caused any
problems on the 2002 machines.

Good luck.

Ken
Norfolk, Va.