The databinding for WinSchedule has been broken in the recent fix for 2008.1 and the current 2008.2.
I have a program shows the calendar by team and there is an option to change the teams. This cause the dataset to load with new employe and appointments. In the past the control would just refresh with the new employees and appointments but now it will not change the employees shown on screen and then will not longer show appointments if yo change the team back to the one that was orginally showing.
I've had to roll back to 2008.1 pre fixes.
Just wanted you guys to be sure that you test your application completely before rolling them out afer 2008.2.
I always wonder how these ones get past infragistics QA cause the fixes sit with them for months
Thanks. I added DataBindingsForOwners.DataSource = Nothing
and that fixed it for now. I also opened a problem ticket.
Roger
Brian Fallon"] That sounds like you bound the RecurrenceIdMember to an integer field; the field to which you bind the RecurrenceId property needs to be able to handle a GUID.
That sounds like you bound the RecurrenceIdMember to an integer field; the field to which you bind the RecurrenceId property needs to be able to handle a GUID.
Not at all... The only thing that has changed is the infragistics control. I've looked at the code between 2008.1 and 2008.2 and the databinding has had alot of work done to it. i think it's been broken.
Brian Fallon"] This is a peer-to-peer newsgroup. If you need a bug fixed you should report the issue via the web support form so you can provide the details necessary in order to reproduce it.
This is a peer-to-peer newsgroup. If you need a bug fixed you should report the issue via the web support form so you can provide the details necessary in order to reproduce it.
It takes over 6 months for support to fix problems like this. The QA team really takes there time checking for bugs :)
Just wanted other users to know about the issue so it can be avoided.
DataBindingsForOwners.DataSource = Nothing and then back to the orginal dataset
This is also a error that pops up from time to time now
Input string was not in a correct format.Couldn't store <2a102105-389a-457e-aab0-656a34d0585b> in EmployeeID Column. Expected type is Int32.