Can Property Nodes cause race conditions?

[Broken_Arrow]

I posted a question on this forum last week regarding highlighting a table programmatically. I received an excellent response re: initializing the shift register, but that wasn't my only problem... I just fixed the VI "by accident". I left the problem behind for a few hours and did some "cleanup" work on the diagram. Upon running the VI again, the problem was gone. I traced the source of the trouble to a Property Node. At one time, I had two property nodes linked to the table: one doing a Disable function and the other doing a EditPos read. Combining these two solved the problem. Seems like a race condition. Can Property Node cause said condition?

[Dennis_Knutson]

The MISuse of property nodes as well as local/global variables can cause race conditions. Its important to use the error in/error out connectors to enforce the correct data flow. While its almost impossible to do a sophisticated user interface without using them, they can cause all sorts of problems.

[Broken_Arrow]

Error in/error out... I'm not even USING those things, but I am aware that they force program flow on sub-VI's, so they'd do the same thing with Nodes. Thanks for the hint.