Exception on date fields

Discussion of open issues, suggestions and bugs regarding IBDAC (InterBase Data Access Components) for Delphi, C++Builder, Lazarus (and FPC)
Post Reply
tolandale
Posts: 2
Joined: Tue 19 Dec 2017 03:29

Exception on date fields

Post by tolandale » Tue 19 Dec 2017 03:46

I had program based on IBX components and it works fine. Now I changed to IBDAC, everything
works fine also, except date fields. For example code like:
dpBirthdate.Date := FieldByName('BIRTH').AsDateTime
works fine with IBX, but the same database, the same records with IBDAC giving me exception with the message something like "-757894579 is invalid timestamp" though in IBX and IBExpert program there is valid values in this field.

Also in DBGrid date fields are showed in strange format like '12.06.632327' though in fields properties I setup clearly date format

Is there some secret parameters I need to change to make it work?

Thanks in advance

ViktorV
Devart Team
Posts: 2780
Joined: Wed 30 Jul 2014 07:16

Re: Exception on date fields

Post by ViktorV » Tue 19 Dec 2017 10:44

Unfortunately we could not reproduce the issue on the latest IBDAC 6.1.4 version.
Please check whether the problem occurs on the latest version IBDAC 6.1.4 and inform us about the result. It it is, please compose a small sample demonstrating the described behavior and send it to us via e-support form: https://www.devart.com/company/contactform.html, including scripts for creating database objects.

tolandale
Posts: 2
Joined: Tue 19 Dec 2017 03:29

Re: Exception on date fields

Post by tolandale » Wed 20 Dec 2017 02:25

The error happened with version 6.0.2
It is interesting that error arrives with Firebird 1.5, but the same database, converted to Firebird 3.0
is not giving the errors with the same code

ViktorV
Devart Team
Posts: 2780
Joined: Wed 30 Jul 2014 07:16

Re: Exception on date fields

Post by ViktorV » Mon 25 Dec 2017 08:22

When testing, we could not reproduce the error.
You are the only user who addressed us with such a problem. To understand the cause of the problem, we need a test case or a description of the steps and the environment in which the problem is reproduced stably. As soon as we get this example and if the cause of the problem is in the code of our product, we will try to fix it in the shortest possible time.

Post Reply