Looking to see if someone can help point me in the right direction with
determining why my spreadsheet (VERY large with a lot of ranges, variables)
is acting up. Up until recently the model worked perfect, recently I added
some model protection and user sign-on requirements, but dont have any
conflicts Im can see.

The issue: Some of my ranges are not updating, its like the model is not
recalculating or updating the ranges after each use. The user selects a
state from a dropdown box, the value 1 = Alabama, 2 = Arkansas, and so on,
the value is assigned to a named range, which drives pivot tables, the coping
of other ranges and so on. While doing some debugging, I noticed that the
named ranges are keeping the previous value.

Thanks for any help

My standard list. Do look at 4 (don't skip the rest).

--
Kind regards,

Niek Otten


Cells not calculating (correctly)

Most frequent causes:

1. Calculation is set to Automatic. This may have happened unintentionally, for example by opening another workbook first.
Calculation is an Excel-wide setting; the first workbook opened determines the calculation mode, which then applies to all
open workbooks and workbooks that are opened later in that instance of Excel. It can be changed manually (again, for all open
workbooks):
ToolsOptionsCalculation tab, check Automatic.
2. There are User Defined Functions (UDFs) which access cells directly from within the function, that is, not via the
argument list. Then Excel is not aware of the need of recalculation. You can include Application.Volatile in the function, but
there is no guarantee this will always calculate cells in the correct sequence in all (future) versions of Excel. Really the best
way is to include all precedent cells in the argument list.
3. Excel version 5.0a (yes, very, very old!) has serious recalculation bugs, Excel 97 absolutely needs Service Pack 2 (SP2)
to calculate correctly.
4. Very, very rarely, Excel's dependency tree gets messed up. One way to rebuild it is to find and replace all "=" by "=",
for all sheets. Later versions of Excel rebuild by pressing CTRL+ALT+SHIFT+F9
5. For many calculation secrets, visit Charles William's site:
www.decisionmodels.com


"Gardfd" wrote in message ...
Looking to see if someone can help point me in the right direction with
determining why my spreadsheet (VERY large with a lot of ranges, variables)
is acting up. Up until recently the model worked perfect, recently I added
some model protection and user sign-on requirements, but don't have any
conflicts I'm can see.

The issue: Some of my ranges are not updating, it's like the model is not
recalculating or updating the ranges after each use. The user selects a
state from a dropdown box, the value 1 = Alabama, 2 = Arkansas, and so on,
the value is assigned to a named range, which drives pivot tables, the coping
of other ranges and so on. While doing some debugging, I noticed that the
named ranges are keeping the previous value.

Thanks for any help

Okay, Niek, spill the beans. Why didn't the text of your response get
truncated into short lines as does everyone else's? <G

Bob

"Niek Otten" wrote in message
...
My standard list. Do look at 4 (don't skip the rest).

--
Kind regards,

Niek Otten


Cells not calculating (correctly)

Most frequent causes:

1. Calculation is set to Automatic. This may have happened
unintentionally, for example by opening another workbook first.
Calculation is an Excel-wide setting; the first workbook opened
determines the calculation mode, which then applies to all
open workbooks and workbooks that are opened later in that instance of
Excel. It can be changed manually (again, for all open
workbooks):
ToolsOptionsCalculation tab, check Automatic.
2. There are User Defined Functions (UDFs) which access cells
directly from within the function, that is, not via the
argument list. Then Excel is not aware of the need of recalculation. You
can include Application.Volatile in the function, but
there is no guarantee this will always calculate cells in the correct
sequence in all (future) versions of Excel. Really the best
way is to include all precedent cells in the argument list.
3. Excel version 5.0a (yes, very, very old!) has serious
recalculation bugs, Excel 97 absolutely needs Service Pack 2 (SP2)
to calculate correctly.
4. Very, very rarely, Excel's dependency tree gets messed up. One
way to rebuild it is to find and replace all "=" by "=",
for all sheets. Later versions of Excel rebuild by pressing
CTRL+ALT+SHIFT+F9
5. For many calculation secrets, visit Charles William's site:
www.decisionmodels.com


"Gardfd" wrote in message
...
Looking to see if someone can help point me in the right direction with
determining why my spreadsheet (VERY large with a lot of ranges,
variables)
is acting up. Up until recently the model worked perfect, recently I
added
some model protection and user sign-on requirements, but don't have any
conflicts I'm can see.

The issue: Some of my ranges are not updating, it's like the model is
not
recalculating or updating the ranges after each use. The user selects
a
state from a dropdown box, the value 1 = Alabama, 2 = Arkansas, and so
on,
the value is assigned to a named range, which drives pivot tables, the
coping
of other ranges and so on. While doing some debugging, I noticed that
the
named ranges are keeping the previous value.

Thanks for any help

Hi Bob,

I wish I knew!

It does here.
I've been struggling with template replies for some time now. If I use Word, I get double spaced lines, maybe you don't?
If I paste to Excel and paste from there into OE, it looks fine here (of course I tested a private reply first!)
Do you ever use pre-cooked replies and if so, how?

--
Kind regards,

Niek Otten

"Bob Phillips" wrote in message ...
Okay, Niek, spill the beans. Why didn't the text of your response get
truncated into short lines as does everyone else's? <G

Bob

"Niek Otten" wrote in message
...
My standard list. Do look at 4 (don't skip the rest).

--
Kind regards,

Niek Otten


Cells not calculating (correctly)

Most frequent causes:

1. Calculation is set to Automatic. This may have happened
unintentionally, for example by opening another workbook first.
Calculation is an Excel-wide setting; the first workbook opened
determines the calculation mode, which then applies to all
open workbooks and workbooks that are opened later in that instance of
Excel. It can be changed manually (again, for all open
workbooks):
ToolsOptionsCalculation tab, check Automatic.
2. There are User Defined Functions (UDFs) which access cells
directly from within the function, that is, not via the
argument list. Then Excel is not aware of the need of recalculation. You
can include Application.Volatile in the function, but
there is no guarantee this will always calculate cells in the correct
sequence in all (future) versions of Excel. Really the best
way is to include all precedent cells in the argument list.
3. Excel version 5.0a (yes, very, very old!) has serious
recalculation bugs, Excel 97 absolutely needs Service Pack 2 (SP2)
to calculate correctly.
4. Very, very rarely, Excel's dependency tree gets messed up. One
way to rebuild it is to find and replace all "=" by "=",
for all sheets. Later versions of Excel rebuild by pressing
CTRL+ALT+SHIFT+F9
5. For many calculation secrets, visit Charles William's site:
www.decisionmodels.com


"Gardfd" wrote in message
...
Looking to see if someone can help point me in the right direction with
determining why my spreadsheet (VERY large with a lot of ranges,
variables)
is acting up. Up until recently the model worked perfect, recently I
added
some model protection and user sign-on requirements, but don't have any
conflicts I'm can see.

The issue: Some of my ranges are not updating, it's like the model is
not
recalculating or updating the ranges after each use. The user selects
a
state from a dropdown box, the value 1 = Alabama, 2 = Arkansas, and so
on,
the value is assigned to a named range, which drives pivot tables, the
coping
of other ranges and so on. While doing some debugging, I noticed that
the
named ranges are keeping the previous value.

Thanks for any help

Hi Niek,

No, I just use the bog-standard reply mechanism (excuse my gutter English).
I was hoping you had the solution, because we get so many problems with
wrap-around in code that it would solve.

Regards

Bob

"Niek Otten" wrote in message
...
Hi Bob,

I wish I knew!

It does here.
I've been struggling with template replies for some time now. If I use
Word, I get double spaced lines, maybe you don't?
If I paste to Excel and paste from there into OE, it looks fine here (of
course I tested a private reply first!)
Do you ever use pre-cooked replies and if so, how?

--
Kind regards,

Niek Otten

"Bob Phillips" wrote in message
...
Okay, Niek, spill the beans. Why didn't the text of your response get
truncated into short lines as does everyone else's? <G

Bob

"Niek Otten" wrote in message
...
My standard list. Do look at 4 (don't skip the rest).

--
Kind regards,

Niek Otten


Cells not calculating (correctly)

Most frequent causes:

1. Calculation is set to Automatic. This may have happened
unintentionally, for example by opening another workbook first.
Calculation is an Excel-wide setting; the first workbook opened
determines the calculation mode, which then applies to all
open workbooks and workbooks that are opened later in that instance of
Excel. It can be changed manually (again, for all open
workbooks):
ToolsOptionsCalculation tab, check Automatic.
2. There are User Defined Functions (UDFs) which access cells
directly from within the function, that is, not via the
argument list. Then Excel is not aware of the need of recalculation.
You
can include Application.Volatile in the function, but
there is no guarantee this will always calculate cells in the correct
sequence in all (future) versions of Excel. Really the best
way is to include all precedent cells in the argument list.
3. Excel version 5.0a (yes, very, very old!) has serious
recalculation bugs, Excel 97 absolutely needs Service Pack 2 (SP2)
to calculate correctly.
4. Very, very rarely, Excel's dependency tree gets messed up. One
way to rebuild it is to find and replace all "=" by "=",
for all sheets. Later versions of Excel rebuild by pressing
CTRL+ALT+SHIFT+F9
5. For many calculation secrets, visit Charles William's site:
www.decisionmodels.com


"Gardfd" wrote in message
...
Looking to see if someone can help point me in the right direction
with
determining why my spreadsheet (VERY large with a lot of ranges,
variables)
is acting up. Up until recently the model worked perfect, recently I
added
some model protection and user sign-on requirements, but don't have
any
conflicts I'm can see.

The issue: Some of my ranges are not updating, it's like the model
is
not
recalculating or updating the ranges after each use. The user
selects
a
state from a dropdown box, the value 1 = Alabama, 2 = Arkansas, and
so
on,
the value is assigned to a named range, which drives pivot tables,
the
coping
of other ranges and so on. While doing some debugging, I noticed
that
the
named ranges are keeping the previous value.

Thanks for any help

In outlook express

Tools Options Send Plain text settings

OE allows up to 132 chars... (default is 72)

********10********20********30********40********50 ********60********70******
**80********90*******100*******110*******120****** *130********

Tim

--
Tim Williams
Palo Alto, CA


"Bob Phillips" wrote in message
...
Hi Niek,

No, I just use the bog-standard reply mechanism (excuse my gutter
English).
I was hoping you had the solution, because we get so many problems with
wrap-around in code that it would solve.

Regards

Bob

"Niek Otten" wrote in message
...
Hi Bob,

I wish I knew!

It does here.
I've been struggling with template replies for some time now. If I use
Word, I get double spaced lines, maybe you don't?
If I paste to Excel and paste from there into OE, it looks fine here (of
course I tested a private reply first!)
Do you ever use pre-cooked replies and if so, how?

--
Kind regards,

Niek Otten

"Bob Phillips" wrote in message
...
Okay, Niek, spill the beans. Why didn't the text of your response get
truncated into short lines as does everyone else's? <G

Bob

"Niek Otten" wrote in message
...
My standard list. Do look at 4 (don't skip the rest).

--
Kind regards,

Niek Otten


Cells not calculating (correctly)

Most frequent causes:

1. Calculation is set to Automatic. This may have happened
unintentionally, for example by opening another workbook first.
Calculation is an Excel-wide setting; the first workbook opened
determines the calculation mode, which then applies to all
open workbooks and workbooks that are opened later in that instance
of
Excel. It can be changed manually (again, for all open
workbooks):
ToolsOptionsCalculation tab, check Automatic.
2. There are User Defined Functions (UDFs) which access cells
directly from within the function, that is, not via the
argument list. Then Excel is not aware of the need of recalculation.
You
can include Application.Volatile in the function, but
there is no guarantee this will always calculate cells in the correct
sequence in all (future) versions of Excel. Really the best
way is to include all precedent cells in the argument list.
3. Excel version 5.0a (yes, very, very old!) has serious
recalculation bugs, Excel 97 absolutely needs Service Pack 2 (SP2)
to calculate correctly.
4. Very, very rarely, Excel's dependency tree gets messed up.
One
way to rebuild it is to find and replace all "=" by "=",
for all sheets. Later versions of Excel rebuild by pressing
CTRL+ALT+SHIFT+F9
5. For many calculation secrets, visit Charles William's site:
www.decisionmodels.com


"Gardfd" wrote in message
...
Looking to see if someone can help point me in the right direction
with
determining why my spreadsheet (VERY large with a lot of ranges,
variables)
is acting up. Up until recently the model worked perfect, recently
I
added
some model protection and user sign-on requirements, but don't have
any
conflicts I'm can see.

The issue: Some of my ranges are not updating, it's like the model
is
not
recalculating or updating the ranges after each use. The user
selects
a
state from a dropdown box, the value 1 = Alabama, 2 = Arkansas, and
so
on,
the value is assigned to a named range, which drives pivot tables,
the
coping
of other ranges and so on. While doing some debugging, I noticed
that
the
named ranges are keeping the previous value.

Thanks for any help