enum conflict - I went from 4 items to 40, now I have a conflict...

[Daddy-O]

I started with, an enum constant to select which of 4 stations I monitor / update. . When I added 36 more, I came up with a conflict. It says "You have two or more enumeration data types wired together, but the enumerations are different. The list of items in the enumerations must be exactly the same".

 I just noticed that on the original "main" program, there are coercion dots on all if the indexes of index arrays (by the way, the original VI is one that was passed along to me as a template of sorts). How do I coerce that index to be accepted? Is that what is causing my error??? The fact that they are coerced on the original but not on the one I have modified, or is that unrelaated?

 Looking forward to input.

Chris (Daddy-O)

[mikeporter]

It sorta sound like you haven't used the typedef everywhere you think you did - or your control isn't saved as a typedef. There is a difference between a customized control and an enumerated type. You can save an enum as a control without defining it as a typedef. So first of all open the enumerated type control and make sure it is being saved as a typedef or strict typedef. Then go and replace the control with the typedef in all the places where you have either dots or broke wires.

Mike..

[Daddy-O]

Mike,

I changed the control on my main VI to a strict type def... Still had broken wires. I realized that the same control was also in a sub VI. Changed it, and all of my broken wires are gone. I am still a very long way from my destination, but you gotta love that unbroken white arrow!!! Thanks for your help.

Chris (Daddy-O)