Bill;

I agree .NULL. takes some getting used to, and break lots of things. Unfortunately, I think that so many are using SQL Server as their back end, there's no avoiding it.

Thanks for taking the time to check it out. As far as 'expected behaviour', I'd suggest that the display respects the 'SET NULLDISPLAY' setting, and that you may need another logical property lallownulldate - just for your future consideration.

>(sigh) I hate NULLs. :-) That's why I rarely let fields be NULL unless there is a specific and compelling reason.
>
>I did take a few minutes to quickly look at this. The best quick workaround I can suggest for this is to create a secondary varable or property to be the control source for the control. Test for ISNULL() on the actual control source and if it is NULL, assign a blank date to the secondary control source. When ready to save the actual data ( if it has changed from blank date ) store the new date to the actual control source and save. A workaround and pain I know, but the best I can suggest at this point. NULL's are just a pain in the neck to deal with. :-)
>
>Bill
>
>>Bill, I'm having a little trouble using the control. I have it working successfully in a modal form (it's great - thank you), but not in the main window.
>>
>>I have the controlsource set to an object property, which is a date value - but upon form instantiation, the value is likely to be blank or null. Is it possible that this is breaking the class?
>>
>>The symptom is that the displayed value of the control is ".NULL." I have used the VFP debugger to verify the controlsource property, and the value of the object property used as the controlsource.
>>
>>Help!
>>
>>>For those of you using my VFP Date and Datetime Pickers classes, I have uploaded a new set of the classes called VFPX Date and Datetime Picker classes stored in DatePickX.zip. This is a 100% VFP solution to the date and datetime picker issue. Functionality is the same as the original classes but the MS MonthView ActiveX control used on the original date and datetime pickers has been replaced with a VFP Calendar class. The Calendar class was designed to be visually similar to the MonthView control and has similar basic functionality. This class is housed in its own class library wich can also be instantiated as a standalone Calendar. A subclass of the Calendar class is also included which has some automatic resizing capability to be used in standalone Calendar scenarios. Documentation for the Calendar class is included for ease of use and extensibility.
>>>
>>>The purposes of creating this new class are to relieve some of the issues some have experienced regarding deploying and instantiating the ActiveX control and also since the Calendar class is fully VFP it can be modified, subclassed or given as much extended functionality as required by the developer. The Calendar control was developed specifically to replace the MS MonthView control on the date and datetime picker class so it does not have the same range of functionality as the MonthView control. On the other hand, since it is VFP, developers will be able to give it all the functionality they need for their particular situations.
>>>
>>>If you do use it, I hope you find it useful. :-)
>>>
>>>Bill