I've upgraded from V4RB 9.6.4 to the latest version via the Omegabundle. I am using MacOS Big Sur 11.6.
I notice in the release notes that there is a change to support the Xojo DateTime field.
I am finding that if I simply read a Vdatetime field from a cursor, it will display as 1970-01-01 if the field is NULL, but correctly if not NULL.
If I check for NULL on a Vdatetime field that is NULL and has NOT been updated using V4RB 11.4.5 then all is ok. But, if I update the same Vdatetime field, and then check for NULL again, I get a hard crash of my app in the debugger.
Here is the line of code where the crash occurs:
If cursor.DateTimeField(pnFld).IsNull Then
My question is to ask if there is something I need to do to the DateTime fields after conversion? I really can't believe that this is a bug in Valentina (although I wouldn't rule it out) because I would think others would have reported this long ago.
I am not having the same problems with my VDate fields.