8.5 crashing

[delbertson]

Yesterday I recieved a copy of Labview 8.5 and installed it, and worked away no problem.  I'm running Windows XP - sp2

This morning as I edited a strict typedef, a cluster of control referances, when Labview crashed.  I have isolated the problem to one file i.e I re-named it and ignored it as when I loaded in my other VI's.

I decided to try and re-create it but everytime I do Labview crashes again.  I have attached the offending VI.  I also have the Windows fault log file if anyone knows how to interprete them.

Anybody got any idea's of what's going wrong and how I can fix it?

Thanks in advance.

Derek

[delbertson]

Further to my last post....

It seems that Labview only crashes when I re-create the typedef and name it exactly the same as the original file.  Give it a different name... and it' ok ????

[PJS]

Opened no problem for me. Although when I have found this in the past (usually related to a disk issue), I have re-created it. Saved it for a previous version, then reopened, and resaved.  That usually has worked in the past for me. 

[delbertson]

Thanks for replying Paul.

Ended up re-creating it and saving under a different name, then went through my project and replaced the instances that weren't found.  I seem to be back on track. You fix sounds much easier though, so if it happens again I'll keep your fix in mind.

Thanks again.

Derek

[delbertson]

Encountered the same thing again with  a different type-def.

This is what I'm doing.  I have a load of referances to front panel objects, most of which are strict type-defs.  I'm bundelling them into a cluster, then creating a control from the terminal and saving that as a strict type def.  Now when I edit any of the items on my front panel I need to edit/update my type def.  As soon as I try and save this new type def over the last one, Labview crashes.  If I try and open any VI that uses this type def Labview crashes.  Though I can open the type-def itself.

Tried saving as a previous version then doing a Save as suggested by Paul but this didn't work.  When this happened earlier I worked round it by re-naming the file so Labview couldn't find, loaded all the VI's and did a manual replace... it works but it takes a while.

Derek

[JamesC]

Hi Derek,

This was reported to R&D (# 4CU3C5QW) for further investigation.
You have already described a possible work around for the moment, although it is long winded.
What I have found during muy investigation is that if I don't run the VI first then I can edit the control, so another possible workaround is to restart labVIEW every time you want to make a change to one of these clusters.

Thank you for making LabVIEW an even better product.

Regards
JamesC
NIUK and Ireland