Z
zsplash
I have an Excel spreadsheet, that is automatically modified (opened and
closed through VBA code) by a single-user. Other people need to have access
to this spreadsheet all the time (and the updates this single-user makes to
it) -- hence, the opening and closing of the spreadsheet. I made the
single-user the only one with write-permission, hoping that would avoid
problems if other users have the spreadsheet open when the single-user is
trying to modify the spreadsheet (through code).
So, if another user has the spreadsheet open, the single-user's
modifications do not "take" and the single-user gets a "file is already
opened" kind of message, asking if he wants to open read-only. Will my
making this a shared file, which I have not done, (with only the single-user
having write-permission) overcome this problem? If not, how can I solve the
problem?
TIA
closed through VBA code) by a single-user. Other people need to have access
to this spreadsheet all the time (and the updates this single-user makes to
it) -- hence, the opening and closing of the spreadsheet. I made the
single-user the only one with write-permission, hoping that would avoid
problems if other users have the spreadsheet open when the single-user is
trying to modify the spreadsheet (through code).
So, if another user has the spreadsheet open, the single-user's
modifications do not "take" and the single-user gets a "file is already
opened" kind of message, asking if he wants to open read-only. Will my
making this a shared file, which I have not done, (with only the single-user
having write-permission) overcome this problem? If not, how can I solve the
problem?
TIA