09-10-2009 09:01 PM
09-11-2009 02:44 AM
Hey,
Do you have the 8.6.1f1 patch installed?
For me it sounds similar to one of the problems fixed there.
Christian
09-11-2009 02:46 PM
Hey bjlv,
Just to walk through how you are setting the user input limits; Are you right clicking on the control and going to Properties»Data Entry and then setting these parameters there?
Does this same behavior occur with other data types? Does this same behavior still occur if you use property nodes to programmatically set the various properties? Does everything seem to work as it should in the development environment?
Sorry to answer a question with a series of questions. But perhaps, if nothing else, a work around can be found.
09-11-2009 02:58 PM
Q
This only happens in the built app or do you see the same thing in the development environment?
Ben
09-14-2009 08:33 AM
Hi All:
I was out dealing with a sick daughter on Friday, but I have had a chance to work on this enough to now know that I was seeing the 8.6.1 bug referenced by the patch Christian_M said I needed. I actually implemented the property node workaround first, and I will test the patch next, as that is a faster way to ship a program minutes from its deadline. Anyway, thanks all for the assistance on this, and I will have to also look into why my search of NI.com didn't turn up this problem when I looked last week. I suppose I didn't use just the right keywords in my search.
bjlv