Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I upgraded one project from XE to XE2 and I noticed that DateToStr doesn’t work exactly as before.
If I try to covert a null date to str it gives “Invalid floating point operation”. While this was not there in XE.
Why there is this difference? Are there similar behaviours for other functions? (I mean some function that in a similar case = converting a null value changes the behaviour)
After investigating I realized that this design choice made by Embarcadero in XE2 will affect a lot of old code. Wherever possible I replaced
DateTimeToStror I added checks forNULLdates before trying to convert to string.Also DevExpress have some problems with their components because of this issue.