I have an Excel program that contains approximately 35 sheets and more than
8MB of info. There are about 350 people that have access to it.

The program is located on a server. I have given access privileges (Read
Only) to everyone, except for 7 staff, who have read/write.

My problem is that the seven people who have r/w are in two different
locations. When one logs off the program, it periodically locks the program
up so no one can log in. We have to call out server people to reset
everything so we can access it. The program is important and it's run 24/7.

Is anyone familiar with this or have any idea what may be causing it and,
even more importantly, how to stop it??

Any help would truly be appreciated! Thank you in advance.

Mark

It doesn't sound like this is a shared workbook. Have you tried making it a
shared workbook, or perhaps moving the entire contents of the workbook into a
new workbook to see if that makes a difference?

"Bruise" wrote:

I have an Excel program that contains approximately 35 sheets and more than
8MB of info. There are about 350 people that have access to it.

The program is located on a server. I have given access privileges (Read
Only) to everyone, except for 7 staff, who have read/write.

My problem is that the seven people who have r/w are in two different
locations. When one logs off the program, it periodically locks the program
up so no one can log in. We have to call out server people to reset
everything so we can access it. The program is important and it's run 24/7.

Is anyone familiar with this or have any idea what may be causing it and,
even more importantly, how to stop it??

Any help would truly be appreciated! Thank you in advance.

Mark

I'm worried that with several people making changes in a shared workbook
that the changes won't take effect immediately, which I need them to do.
Also, if a user has read only access to the directory, will they be able to
make changes in a shared workbook?

Another problem is that my macros and VBA code is disabled in a shared
workbook. The workbook relies heavily upon VBA/macro use.

Am I correct or do I read the Shared Workbook process wrong? I'm not
totally familiar with it and I haven't used it before.

Thanks much for your help.


"ajvasel" wrote in message
...
It doesn't sound like this is a shared workbook. Have you tried making it
a
shared workbook, or perhaps moving the entire contents of the workbook
into a
new workbook to see if that makes a difference?

"Bruise" wrote:

I have an Excel program that contains approximately 35 sheets and more
than
8MB of info. There are about 350 people that have access to it.

The program is located on a server. I have given access privileges (Read
Only) to everyone, except for 7 staff, who have read/write.

My problem is that the seven people who have r/w are in two different
locations. When one logs off the program, it periodically locks the
program
up so no one can log in. We have to call out server people to reset
everything so we can access it. The program is important and it's run
24/7.

Is anyone familiar with this or have any idea what may be causing it and,
even more importantly, how to stop it??

Any help would truly be appreciated! Thank you in advance.

Mark

I can understand your concerns about using a shared workbook. I'm not a fan
of them myself, but we have had to use them on occasion.

A user cannot make a change in a shared workbook unless they open up a live
version (I'm assuming you're using password protection).

I'm wondering why macros are disabled - I'm guessing that they utilize
certain functions made unavailble in a shared workbook (like merge cells).

Did you try moving the contents of the workbook into a new workbook just in
case there is some sort of glitch in the original workbook?

"Bruise" wrote:

I'm worried that with several people making changes in a shared workbook
that the changes won't take effect immediately, which I need them to do.
Also, if a user has read only access to the directory, will they be able to
make changes in a shared workbook?

Another problem is that my macros and VBA code is disabled in a shared
workbook. The workbook relies heavily upon VBA/macro use.

Am I correct or do I read the Shared Workbook process wrong? I'm not
totally familiar with it and I haven't used it before.

Thanks much for your help.


"ajvasel" wrote in message
...
It doesn't sound like this is a shared workbook. Have you tried making it
a
shared workbook, or perhaps moving the entire contents of the workbook
into a
new workbook to see if that makes a difference?

"Bruise" wrote:

I have an Excel program that contains approximately 35 sheets and more
than
8MB of info. There are about 350 people that have access to it.

The program is located on a server. I have given access privileges (Read
Only) to everyone, except for 7 staff, who have read/write.

My problem is that the seven people who have r/w are in two different
locations. When one logs off the program, it periodically locks the
program
up so no one can log in. We have to call out server people to reset
everything so we can access it. The program is important and it's run
24/7.

Is anyone familiar with this or have any idea what may be causing it and,
even more importantly, how to stop it??

Any help would truly be appreciated! Thank you in advance.

Mark