[OT Too far]

[paul_cardinale]

What rocket scientist thought this would be a useful error message?

[aputman]

When those pesky bugs keep showing up and you aren't sure what's causing them or how to fix them, it's more "professional" to show a generic error message that means nothing than to let the program crash and burn. 

[billko]

Too emotionally insecure to call it an "unknown" error!  😄

[PiDi]

Well, it just states that your project is too generic for LabVIEW... 

[JaredT]

Hi paul_cardinale,

Generic errors are used because it is very hard to foresee every possible issue users may encounter while using LabVIEW. There are nearly infinite possible architecture options when creating a VI. 

If you can provide some details about your code and when this error is occurring, I may be able to help diagnose the issue.

Regards,

 Jared T.

 Applications Engineer

[paul_cardinale]

I have a project that contains several classes.  A number of the classes are child classes, some of them nested 3 deep.

I changed the name of a dynamic dispatch acsessor VI.  For some of the VIs, Save as,,, worked OK; but for a couple of them I had trouble, so I tried deleting them then adding them back.  It was when I tried adding a file to a class that the error occurred.  The next day I tried again and it worked OK.

[paul_cardinale]

---

@PiDi wrote:

Well, it just states that your project is too generic for LabVIEW... 

---

When I create code, if it's reasonable, I try to make it generic (I like reusability).  I guess I just went too far.

[Ben]

---

@paul_cardinale wrote:

---

@PiDi wrote:

Well, it just states that your project is too generic for LabVIEW... 

---

When I create code, if it's reasonable, I try to make it generic (I like reusability).  I guess I just went too far.

---

Spoiler

After reading your posts over the years I have to ask "Is there any question that you went too far?".

Ben

[paul_cardinale]

I like to try pushing every button I find.