SWEET!

What version of DevExpress is used in the wrapper in 1.6.1?

Yes.

Has this issue been resolved in 1.6.1?

Ok, Thanks.

Not yet.  There is a .NET issue with the DateTimePicker and rendering when Themes are not available under certain instantiation criteria, so we are still investigating and trying to come up with a viable solution (without writing our own DateTimePicker control) .

Just wondering if there is any news on this issue as I just ran into this error myself?

Thanks

Thanks for the infor...it does look like the DateTimePicker is relying on the Visual Styles for rendering....hmmmm, I will have to work on this

You can reproduce the problem in Windows XP by setting the Windows theme to 'Windows Classic". Attached is an example of how the error manifests itself when the application is using ES as the data source (My app is called BathcTracker). I looked up Event Type: clr20r3 in the Microsoft knowledge base and it returned article 911816 "Unhanded exceptions cause ASP.Net-based application to unexpectedly quit in the .NET Framework 2.0". You may want to look at the article to see if their resolution is something that should be incorporated in ES to better handle unexpected exceptions.

-Larry

We will setup a Windows 2000 Pro virtual machine and test this to see if there is something that we can do about this.  We just use a standard DateTimePicker, so this is a bit odd...however, we have seen this type of thing before when the Visual Renderers are used within certain environments and the DateTimePicker may be doing something out of context.   We will investigate further.  Thanks.

I just tripped into this issue when I tried to deploy my application to a PC running Windows 2000 Pro. The application aborts with a Visual Styles error when the user selects a browse dialog that contains a DateTimePicker control. (When running with the ES server the program aborts with an unhandled exception) However if create an new SF application with a single form that contains a standard MS DateTimePicker or a SF DateTimePicker and run the application, the controls render properly and I can click on the drop down. It would appear that is something about the way the control is being used in the browse dialog that is causing the program to fail. This is an issue for me since I have a lot of Windows 2000 Pro systems.

-Larry