M
mark g
This is a bit of a strange one....I created a workbook and
protected each sheet, as well as the workbook itself, with
a password. This is not a password for opening the
workbook but only to prevent accidental changes to data or
formulas. This workbook is being used by a number of
users throughout my company in different countries.
For some reason none of my colleagues in France are able
to open this. Whenever they try they get a message
telling them that the workbook is password protected and
theyfore unable to be opened. We are using the same
version of Excel (97 for Windows).
I have not been able to figure out what the problem is. I
removed the password protection from each worksheet and
the workbook and this has corrected the problem. However,
I still want to be able to protect the data and formulas.
Any ideas why this is happening?
It is odd because (1) there is not a password set to open
the workbook (2)Excel does not prompt these uses for a
password, but simply tells them that it cannot be opened,
and (3) this problem is not occurring anywhere else.
Thanks,
Mark
protected each sheet, as well as the workbook itself, with
a password. This is not a password for opening the
workbook but only to prevent accidental changes to data or
formulas. This workbook is being used by a number of
users throughout my company in different countries.
For some reason none of my colleagues in France are able
to open this. Whenever they try they get a message
telling them that the workbook is password protected and
theyfore unable to be opened. We are using the same
version of Excel (97 for Windows).
I have not been able to figure out what the problem is. I
removed the password protection from each worksheet and
the workbook and this has corrected the problem. However,
I still want to be able to protect the data and formulas.
Any ideas why this is happening?
It is odd because (1) there is not a password set to open
the workbook (2)Excel does not prompt these uses for a
password, but simply tells them that it cannot be opened,
and (3) this problem is not occurring anywhere else.
Thanks,
Mark