>Patrick,
>
>>I am finding that the mmNumericUpDown control works fine if the up and down arrows are pressed but if the user manually enters a value and without leaving the control, presses save, the values are not saved and are defaulted to the last valid number that was entered (followed by a TAB or ENTER).
>>
>>Is there anyway to fix this validation so that a user can enter in the values manually and then press save without having to TAB (or press Enter) out of the field? The validation doesn't seem to occur if the user doesn't tab or enter on the control.
>
>I verified that this is actually a bug with the Microsoft NumericUpDown control. Fortunately, Microsoft knows about it and hopefully it's fixed in 2.0 (I haven't checked it yet). Here's some information on the problem:
>
>http://www.windowsforms.net/Forums/ShowPost.aspx?tabIndex=1&tabId=41&PostID=5387
>
>Regards,

I created a work around for it so that I can at least lay this one to rest.

I do have one other question that you may be able to answer more quickly than be researching. When you click the new button on the maintenance form, the properties screen comes up partially while the objects instantiate (it appears). Is there an easy way to speed up the instantiation or lock/pause the screen until the entire process is complete? Maybe it is just my slow computer but I could imagine a user getting pretty tired of it. It only happens on the first instantiation. Any new button after that works very quickly.

Pat.