Access2007 "calculating" question

[Mark Andrews]

I built an pretty big Access2007 application, it works pretty good in
general.

One thing I do not like is the time it takes on some of the screens with
"Calculating" in the status bar before it switches back to "form View" or
"Datasheet view".

It seems like any kind of calulated control. Any control with the control
source
set to "= some kind of expression", for example "=Nz([Lastname],"") & ", "
& Nz([Firstname],"")"
can take a very long time until it is shown to the user (10 seconds for
example).
Forget about long datasheets with calulated columns they can take a really
long time (even if the calulations are really simple).

I know I can program thing differently, and not have any calculated
controls, but that causes me more work which is a bad thing.

Anyone have any magical fixes? I tried some of the suggestions on Allen
Browne's web site for Access2007 settings, didn't seem to help.

On vista it seems extra bad.

Thanks in advance,
Mark

 

[Gina Whipp]

Mark,

You know that more thing you mentioned... Well, you could make the
calculations happen in the RecordSource (query) and that would help.

As a side note... I broke my magic wand but hang around maybe some elses is
working!

--
Gina Whipp
2010 Microsoft MVP (Access)

"I feel I have been denied critical, need to know, information!" - Tremors
II

http://www.regina-whipp.com/index_files/TipList.htm

 

[Mark Andrews]

I know that one, any other ideas that would help?

This seems to be a problem that Access2007 has that older versions did not?

Mark

Mark,

You know that more thing you mentioned... Well, you could make the
calculations happen in the RecordSource (query) and that would help.

As a side note... I broke my magic wand but hang around maybe some elses
is working!

--
Gina Whipp
2010 Microsoft MVP (Access)

"I feel I have been denied critical, need to know, information!" - Tremors
II

http://www.regina-whipp.com/index_files/TipList.htm

I built an pretty big Access2007 application, it works pretty good in
general.

One thing I do not like is the time it takes on some of the screens with
"Calculating" in the status bar before it switches back to "form View" or
"Datasheet view".

It seems like any kind of calulated control. Any control with the
control source
set to "= some kind of expression", for example "=Nz([Lastname],"") & ",
" & Nz([Firstname],"")"
can take a very long time until it is shown to the user (10 seconds for
example).
Forget about long datasheets with calulated columns they can take a
really long time (even if the calulations are really simple).

I know I can program thing differently, and not have any calculated
controls, but that causes me more work which is a bad thing.

Anyone have any magical fixes? I tried some of the suggestions on Allen
Browne's web site for Access2007 settings, didn't seem to help.

On vista it seems extra bad.

Thanks in advance,
Mark

 

[Gina Whipp]

Mark,

Unfortunately, no... I know I don't have to ask you about Trusted Locations
and such because I can see by your posts you would have already taken care
of that.

--
Gina Whipp
2010 Microsoft MVP (Access)

"I feel I have been denied critical, need to know, information!" - Tremors
II

http://www.regina-whipp.com/index_files/TipList.htm

I know that one, any other ideas that would help?

This seems to be a problem that Access2007 has that older versions did
not?

Mark

Mark,

You know that more thing you mentioned... Well, you could make the
calculations happen in the RecordSource (query) and that would help.

As a side note... I broke my magic wand but hang around maybe some elses
is working!

--
Gina Whipp
2010 Microsoft MVP (Access)

"I feel I have been denied critical, need to know, information!" -
Tremors II

http://www.regina-whipp.com/index_files/TipList.htm

I built an pretty big Access2007 application, it works pretty good in
general.

One thing I do not like is the time it takes on some of the screens with
"Calculating" in the status bar before it switches back to "form View"
or "Datasheet view".

It seems like any kind of calulated control. Any control with the
control source
set to "= some kind of expression", for example "=Nz([Lastname],"") & ",
" & Nz([Firstname],"")"
can take a very long time until it is shown to the user (10 seconds for
example).
Forget about long datasheets with calulated columns they can take a
really long time (even if the calulations are really simple).

I know I can program thing differently, and not have any calculated
controls, but that causes me more work which is a bad thing.

Anyone have any magical fixes? I tried some of the suggestions on Allen
Browne's web site for Access2007 settings, didn't seem to help.

On vista it seems extra bad.

Thanks in advance,
Mark

 

[Mark Andrews]

Ok I'll try and figure it out. I'll probably end up taking out all
calculated fields and use code to refresh the textbox when appropriate or
put more logic in the query that drives the form.

Simple things like in my form heading I might have = nz([LastName],"") & ",
" & Nz([Firstname],"") and this might take 10 seconds to display under
certain circumstances. Other times it might take under 1 second.

On vista I have seen "calculating" go much longer, same application.

Mark

Mark,

Unfortunately, no... I know I don't have to ask you about Trusted
Locations and such because I can see by your posts you would have already
taken care of that.

--
Gina Whipp
2010 Microsoft MVP (Access)

"I feel I have been denied critical, need to know, information!" - Tremors
II

http://www.regina-whipp.com/index_files/TipList.htm

I know that one, any other ideas that would help?

This seems to be a problem that Access2007 has that older versions did
not?

Mark

Mark,

You know that more thing you mentioned... Well, you could make the
calculations happen in the RecordSource (query) and that would help.

As a side note... I broke my magic wand but hang around maybe some
elses is working!

--
Gina Whipp
2010 Microsoft MVP (Access)

"I feel I have been denied critical, need to know, information!" -
Tremors II

http://www.regina-whipp.com/index_files/TipList.htm

I built an pretty big Access2007 application, it works pretty good in
general.

One thing I do not like is the time it takes on some of the screens
with "Calculating" in the status bar before it switches back to "form
View" or "Datasheet view".

It seems like any kind of calulated control. Any control with the
control source
set to "= some kind of expression", for example "=Nz([Lastname],"") &
", " & Nz([Firstname],"")"
can take a very long time until it is shown to the user (10 seconds for
example).
Forget about long datasheets with calulated columns they can take a
really long time (even if the calulations are really simple).

I know I can program thing differently, and not have any calculated
controls, but that causes me more work which is a bad thing.

Anyone have any magical fixes? I tried some of the suggestions on
Allen Browne's web site for Access2007 settings, didn't seem to help.

On vista it seems extra bad.

Thanks in advance,
Mark

 

[Gina Whipp]

Mark,

Instead of the Nz() function try ([LastName]+" ") & [FirstName]

If it does load faster then it might be a matter fo *cleaning* up some
expressions to make them more efficient...

--
Gina Whipp
2010 Microsoft MVP (Access)

"I feel I have been denied critical, need to know, information!" - Tremors
II

http://www.regina-whipp.com/index_files/TipList.htm

Ok I'll try and figure it out. I'll probably end up taking out all
calculated fields and use code to refresh the textbox when appropriate or
put more logic in the query that drives the form.

Simple things like in my form heading I might have = nz([LastName],"") &
", " & Nz([Firstname],"") and this might take 10 seconds to display under
certain circumstances. Other times it might take under 1 second.

On vista I have seen "calculating" go much longer, same application.

Mark

Mark,

Unfortunately, no... I know I don't have to ask you about Trusted
Locations and such because I can see by your posts you would have already
taken care of that.

--
Gina Whipp
2010 Microsoft MVP (Access)

"I feel I have been denied critical, need to know, information!" -
Tremors II

http://www.regina-whipp.com/index_files/TipList.htm

I know that one, any other ideas that would help?

This seems to be a problem that Access2007 has that older versions did
not?

Mark
Mark,

You know that more thing you mentioned... Well, you could make the
calculations happen in the RecordSource (query) and that would help.

As a side note... I broke my magic wand but hang around maybe some
elses is working!

--
Gina Whipp
2010 Microsoft MVP (Access)

"I feel I have been denied critical, need to know, information!" -
Tremors II

http://www.regina-whipp.com/index_files/TipList.htm

I built an pretty big Access2007 application, it works pretty good in
general.

One thing I do not like is the time it takes on some of the screens
with "Calculating" in the status bar before it switches back to "form
View" or "Datasheet view".

It seems like any kind of calulated control. Any control with the
control source
set to "= some kind of expression", for example "=Nz([Lastname],"") &
", " & Nz([Firstname],"")"
can take a very long time until it is shown to the user (10 seconds
for example).
Forget about long datasheets with calulated columns they can take a
really long time (even if the calulations are really simple).

I know I can program thing differently, and not have any calculated
controls, but that causes me more work which is a bad thing.

Anyone have any magical fixes? I tried some of the suggestions on
Allen Browne's web site for Access2007 settings, didn't seem to help.

On vista it seems extra bad.

Thanks in advance,
Mark

 

[Mark Andrews]

The microseconds for something like that are not the problem.
Also wouldn't your expression crash if Firstname is null.

It's all over the place with every type of calculated field (basically
calculated fields are displayed after "calculating" is complete).

No worries I'll look at it more in the near future, for the next release of
my product.
Mark

Mark,

Instead of the Nz() function try ([LastName]+" ") & [FirstName]

If it does load faster then it might be a matter fo *cleaning* up some
expressions to make them more efficient...

--
Gina Whipp
2010 Microsoft MVP (Access)

"I feel I have been denied critical, need to know, information!" - Tremors
II

http://www.regina-whipp.com/index_files/TipList.htm

Ok I'll try and figure it out. I'll probably end up taking out all
calculated fields and use code to refresh the textbox when appropriate or
put more logic in the query that drives the form.

Simple things like in my form heading I might have = nz([LastName],"") &
", " & Nz([Firstname],"") and this might take 10 seconds to display under
certain circumstances. Other times it might take under 1 second.

On vista I have seen "calculating" go much longer, same application.

Mark

Mark,

Unfortunately, no... I know I don't have to ask you about Trusted
Locations and such because I can see by your posts you would have
already taken care of that.

--
Gina Whipp
2010 Microsoft MVP (Access)

"I feel I have been denied critical, need to know, information!" -
Tremors II

http://www.regina-whipp.com/index_files/TipList.htm

I know that one, any other ideas that would help?

This seems to be a problem that Access2007 has that older versions did
not?

Mark
Mark,

You know that more thing you mentioned... Well, you could make the
calculations happen in the RecordSource (query) and that would help.

As a side note... I broke my magic wand but hang around maybe some
elses is working!

--
Gina Whipp
2010 Microsoft MVP (Access)

"I feel I have been denied critical, need to know, information!" -
Tremors II

http://www.regina-whipp.com/index_files/TipList.htm

I built an pretty big Access2007 application, it works pretty good in
general.

One thing I do not like is the time it takes on some of the screens
with "Calculating" in the status bar before it switches back to "form
View" or "Datasheet view".

It seems like any kind of calulated control. Any control with the
control source
set to "= some kind of expression", for example "=Nz([Lastname],"") &
", " & Nz([Firstname],"")"
can take a very long time until it is shown to the user (10 seconds
for example).
Forget about long datasheets with calulated columns they can take a
really long time (even if the calulations are really simple).

I know I can program thing differently, and not have any calculated
controls, but that causes me more work which is a bad thing.

Anyone have any magical fixes? I tried some of the suggestions on
Allen Browne's web site for Access2007 settings, didn't seem to help.

On vista it seems extra bad.

Thanks in advance,
Mark

 

[Gina Whipp]

Mark,

Actually no it's designed to handle NULL's hence the '+' symbol. I find it
alot more effective especially when doing names. And when you think aobut
it... those microseconds do tend to add up so every one I can shave off I
do.

Good Luck!
Gina Whipp
2010 Microsoft MVP (Access)

"I feel I have been denied critical, need to know, information!" - Tremors
II

http://www.regina-whipp.com/index_files/TipList.htm

The microseconds for something like that are not the problem.
Also wouldn't your expression crash if Firstname is null.

It's all over the place with every type of calculated field (basically
calculated fields are displayed after "calculating" is complete).

No worries I'll look at it more in the near future, for the next release
of my product.
Mark

Mark,

Instead of the Nz() function try ([LastName]+" ") & [FirstName]

If it does load faster then it might be a matter fo *cleaning* up some
expressions to make them more efficient...

--
Gina Whipp
2010 Microsoft MVP (Access)

"I feel I have been denied critical, need to know, information!" -
Tremors II

http://www.regina-whipp.com/index_files/TipList.htm

Ok I'll try and figure it out. I'll probably end up taking out all
calculated fields and use code to refresh the textbox when appropriate
or put more logic in the query that drives the form.

Simple things like in my form heading I might have = nz([LastName],"") &
", " & Nz([Firstname],"") and this might take 10 seconds to display
under certain circumstances. Other times it might take under 1 second.

On vista I have seen "calculating" go much longer, same application.

Mark


Mark,

Unfortunately, no... I know I don't have to ask you about Trusted
Locations and such because I can see by your posts you would have
already taken care of that.

--
Gina Whipp
2010 Microsoft MVP (Access)

"I feel I have been denied critical, need to know, information!" -
Tremors II

http://www.regina-whipp.com/index_files/TipList.htm

I know that one, any other ideas that would help?

This seems to be a problem that Access2007 has that older versions did
not?

Mark
Mark,

You know that more thing you mentioned... Well, you could make the
calculations happen in the RecordSource (query) and that would help.

As a side note... I broke my magic wand but hang around maybe some
elses is working!

--
Gina Whipp
2010 Microsoft MVP (Access)

"I feel I have been denied critical, need to know, information!" -
Tremors II

http://www.regina-whipp.com/index_files/TipList.htm

I built an pretty big Access2007 application, it works pretty good in
general.

One thing I do not like is the time it takes on some of the screens
with "Calculating" in the status bar before it switches back to
"form View" or "Datasheet view".

It seems like any kind of calulated control. Any control with the
control source
set to "= some kind of expression", for example "=Nz([Lastname],"")
& ", " & Nz([Firstname],"")"
can take a very long time until it is shown to the user (10 seconds
for example).
Forget about long datasheets with calulated columns they can take a
really long time (even if the calulations are really simple).

I know I can program thing differently, and not have any calculated
controls, but that causes me more work which is a bad thing.

Anyone have any magical fixes? I tried some of the suggestions on
Allen Browne's web site for Access2007 settings, didn't seem to
help.

On vista it seems extra bad.

Thanks in advance,
Mark