I pick a date greater then about 25 years (ie, 2040-03-08). It saves it in a MySQL database correctly, but when trying to use this field as the initial date in Calendar2, it displays it as 1969-12-31. If I use a date less then about 25 years in the future it works correctly. Everything "seems" to work just great as long as I don't set a date greater then about 25 years into the future. If I use a plain old date field with the MySQL, it works great... so I don't think I have a problem with the database. Any thoughts?
Yes, the c+30 does allow picking the original date correctly and recording it in the MySQL database correctly, BUT when trying to "update" or reload that same date back into Calendar2 it displays it as 1969-12-31 even though dates less then about 2030 work just fine. It's the updating or "reloading" a date back into Calendar2 that seems to be the problem with dates larger then 25 years into the future.
Thanks for your fast responses. I'm probably not explaining the issue correctly... I'm sometimes not very good at describing issues. I probably should first have said that this problem only started after updating Calendar2 to the recent version on February 8, 2012.
When trying to set the "initial date" in Calendar2 to a valid MySQL date that is already set correctly in MySQL to a very future date such as 2045-03-09, Calendar2 displays it as 1969-12-31 even though it is correct in the MySQL database. I can then set Calendar2 to something like 2050-03-09, it will update the MySQL correctly with exactly that date.
BUT when I pull that same DATE from the MySQL database using it as the initial date in Calendar2, Calendar2 displays it as 1969-12-31 instead of 2050-03-09 even though it is correct in the MySQL database.
This whole issue regarding using dates greater then 25 years into the future only started occuring after the update on February 8, 2012. I don't "think" this has anything to do with the actual MySQL database but something with using a very large "future" date as the Initial Value in the extension itself.
Reverting back to the Calendar extension before the recent update solves the problem.