Hello,
I think there is possible bug with jRDC2 when retrieve date type field.
1) Since jRDC2 return date value as tick, if the value is null, it will raised an error. See this for more detail : https://b4x.com/android/forum/threads/solved-jrdc2-error-handle-null-value-in-date-type-field.93409/
2) This could be consider as a bug or not, depend on your need.
If you have a date field on the database server with value 5/28/18 (dd/MM/yy format), in user device, this value could be remain the same or change into 5/29/18 or others values depends on timezone in that device. If you want this behavior, than it is OK, but if you want the real date value on the server, you need another steps to ensure that date value on the device and server is always the same no matter what timezone is for that device.
I think there is possible bug with jRDC2 when retrieve date type field.
1) Since jRDC2 return date value as tick, if the value is null, it will raised an error. See this for more detail : https://b4x.com/android/forum/threads/solved-jrdc2-error-handle-null-value-in-date-type-field.93409/
2) This could be consider as a bug or not, depend on your need.
If you have a date field on the database server with value 5/28/18 (dd/MM/yy format), in user device, this value could be remain the same or change into 5/29/18 or others values depends on timezone in that device. If you want this behavior, than it is OK, but if you want the real date value on the server, you need another steps to ensure that date value on the device and server is always the same no matter what timezone is for that device.