+1 800 256 3608 (toll-free in North America) or +49 7531 90 60 10| service@combit.com

Problems with empty date values


(Guest) #1

I am using Xbase++ and List & Label 14.

Since upgrading to version 14 from version 12, I have noticed that L&L seems to format a date incorrectly if the date value is empty. If I assign the empty date value to a variable within L&L, it prints a really weird value (example: -7/-15/-18311).

If I put the value within the Date$() function, I get a different incorrect value (example: 4.29e+009).

I tried putting the date within the NullSafe() method, but that didn’t help.

I was able to get around the problem by using the following formula for the date value within my report:

If(Year(PO.ETA_DATE) > 0, Date$(PO.ETA_DATE), ’ ')

Still, I would prefer not to have to put this code around every date value in my reports. I don’t remember L&L having issues with empty date values in version 12.

The empty date values I am trying to print are stored in .DBF tables. I am using Advantage Database Server version 9.1.

Has anyone else experienced a similar problem? Is there a setting I can change with the report that would render empty date values correctly?

Any help will be appreciated. Thanks!

Chris Carmac


(Guest) #2

Which version number of LL14 - e.g. 14.009 - are you using?
I saw in the release notes of version 14.005 follwing entry:

If LL_OPTION_NULL_IS_NONDESTRUCTIVE was set, a NULL date value was displayed
as “01.01.-4713” instead of just an empty string.

Maybe it could help you?

“Chris Carmac” <ccarmac@freedomsoft…> schrieb im Newsbeitrag
news:16232517201021132@combit.net

I am using Xbase++ and List & Label 14.

Since upgrading to version 14 from version 12, I have noticed that L&L
seems to format a date incorrectly if the date value is empty. If I
assign the empty date value to a variable within L&L, it prints a really
weird value (example: -7/-15/-18311).

If I put the value within the Date$() function, I get a different
incorrect value (example: 4.29e+009).

I tried putting the date within the NullSafe() method, but that didn’t
help.

I was able to get around the problem by using the following formula for
the date value within my report:

If(Year(PO.ETA_DATE) > 0, Date$(PO.ETA_DATE), ’ ')

Still, I would prefer not to have to put this code around every date value
in my reports. I don’t remember L&L having issues with empty date values
in version 12.

The empty date values I am trying to print are stored in .DBF tables. I am
using Advantage Database Server version 9.1.

Has anyone else experienced a similar problem? Is there a setting I can
change with the report that would render empty date values correctly?

Any help will be appreciated. Thanks!

Chris Carmac


(Bijan Hosseiny) #3

I have this same issue on one my machines, I remember I may have changed one of the region settings.

My empty dates are coming out as 1/1/-4713.
The following does fix the issue. However, I don’t think it is a practical solution. What setting on the Windows 2012 server is causing this date issue. Is there any other settings in L&L to stop this?

If(Year(PO.ETA_DATE) > 0, Date$(PO.ETA_DATE), ’ ')

Thanks