IE crashes

[Gary L. Chefetz [MVP]]

Paul:

Have you tried deleting all the pj*.* objects in the downloaded programs
folder? Do this through a command prompt rather than through the browser. At
the same time delete all cookies and temporary Internet files. Have you
tried this?

 

[PaulLinscott]

Victor, Gary,

I removed the pj*.* from the downloaded folder, removed the cookies and
internet files. This didn't help. This morning I experimented with the
customized field "Schedule" that I created to see why the customized
field was causing the crash. I initially thought is could be a special
character in the formula or value field, but it wasn't. I then tried to
see if the order in the view had some impact. To my surprise, if I place
the Schedule field in front of the Submitted On field (and upto the Task
Name field), IE crashes. As soon as I placed the Schedule field past the
Submitted field, IE crashes. Why it crashes for some resources is still
a mystery. My only assumption is that it is related to the task data
somehow or perhaps a setting. Remember that the same plans work on the
test server. I did however examined the project plans. The only thing
that seems odd is the Finish Variance column in one plan has a variance
of 277+. I will speak with the PM. All other plans have a variance
between -16 and +27.

Next steps - I have saved the grids of the user that IE crashes and a
user that IE was working OK. I will examine the delta.

If you have any suggestions on what to look for, please let me know.
It's one thing to find what is causing the problem, it is just as
important to find out why it happened.

thanks for your help

Paul

 

[Gary L. Chefetz [MVP]]

Paul:

I must be losing it lately and completely missed the fact that you said you
*created* a field called "schedule." As this is already the name of an
existing field in the database, there's no telling what havoc it can cause.
Call it Schedule Ind or something like that. Don't use existing field names
such as "schedule" and "status."

 

[PaulLinscott]

Gary,

The light just turned on! The actual name of the Custom field i
Schedule. On the test system I called it Schedule Task. That's why i
worked on the test server.
Question - I created 2 custom fields for schedule on the productio
server: 1 on the task level, the other on the project level. Th
formula, graphic indicators and values are the same for both. Th
reason I named the field Schedule and Schedule - project on th
production server was because the system does not allow you to have th
2 custom fields with the same name. The goal is to be able to fla
schedule statuses on the task and project level. Is there a better wa
to accomplish this using only 1 custom field?

Question - When the custom field name is changed. Do I have t
republish all the project plans again in order to use the new name?

thx

Pau

 

[Gary L. Chefetz [MVP]]

Paul:

You need to use two fields, one at the task and one at the Project level. I
suggest that you use different indicators. For instance, if you use circles
at the project level, then use squares at the task level. This provides a
visual marker to instantly know the difference. And, yes you need to
republish the world. For this you might look at the view populator tool
downloadable from Microsoft downloads.

 

[Clara]

Hi Paul

We have this same issue. It is caused by the Google search tool bar. check
and see if the affected users have this installed and uninstall it. This will
solve the problem

Hope this helps

Clara