Hi All,

I have the following problem:
I am working on a UNIX to Windows migration and after the initial installation and transfer of Tools environment the following errors occur
In any Baan IV session whenever a date is inserted or updated we get an error 205 form the system telling hte value is out of range.
The Windows Event log says the following

Env baan (c:\baan)
Prog msql7 file \MSQL\msql_data.c # 769
Keyword Date out of range
Username baan type S language 1
Process 0x1734
Lasterror 997 (Overlapped I/O operation is in progress.)
Errno 0
bdberrno 0
Message
dbs_errno = 205, Error 205 occurred:
bshell date -2147483648 (-2147483648 days) is not supported. The valid supported range of dates are from 02/01/1753 (639907 days) to 31/12/9999 (3652059 days) [dd/mm/yyyy].
DBMS Input: Data out of range for R_GTEQ on dbo.ttdsls038003.
Flushed at \MSQL\msql_row.c : #244.

Is there anybody out here that knows why a wrong date is sent to the database.
An other point is that when I enter a record via ttaad4100 in a table this DOES work and no errors occur.

Any advise is appreciated

Hi,

Please check the following links:
http://www.baanboard.com/baanboard/showthread.php?t=43380&highlight=205
http://www.baanboard.com/baanboard/showthread.php?t=33876&highlight=205

I hope it helps,

- George

Hi,

Please check the following links:
http://www.baanboard.com/baanboard/showthread.php?t=43380&highlight=205
http://www.baanboard.com/baanboard/showthread.php?t=33876&highlight=205

I hope it helps,

- George

Thanks George but hey both do not apply to my problem
But thanks anyway

Alexander

ok, it obviously has to do how null dates are represented in your old system.

Baan in general does not store any null values for any datatype, but has for each datatype a valid value defined, which is interpreted as null. So in old times, the value for a null date was -2 to the power of 32, I think.

Later Baan chanegd this to another value, because this was not compatible to ODBC drivers.

Here must be the root cause of your problem, even though I am confused, since bdbpre/bdbpost should cover this. So here some questions:

On which DB platform is your old system?
What method do you use for transfering the data?

Regards

Markus

SQL2005 requires poorting set 6.1c.07.13 or higher . Probably it's not the case in ur case . It is bshell and MSQL driver converts the date entered by user to db date format . And this in ur case must not be compatible . Upgrade the porting set should resolve ur issue .

What's the db level you are using: we solved error 205 by adding MSQL_LEVEL1=0 to the database/tabledef.

ok, it obviously has to do how null dates are represented in your old system.

Baan in general does not store any null values for any datatype, but has for each datatype a valid value defined, which is interpreted as null. So in old times, the value for a null date was -2 to the power of 32, I think.

Later Baan chanegd this to another value, because this was not compatible to ODBC drivers.

Here must be the root cause of your problem, even though I am confused, since bdbpre/bdbpost should cover this. So here some questions:

On which DB platform is your old system?
What method do you use for transfering the data?

Regards

Markus

Hi,

It was Tbase on UNIX DEC Alpha
I have used bdbpre and bdbpost for the datatransfer.
There is no other way

Thanks Alexander

SQL2005 requires poorting set 6.1c.07.13 or higher . Probably it's not the case in ur case . It is bshell and MSQL driver converts the date entered by user to db date format . And this in ur case must not be compatible . Upgrade the porting set should resolve ur issue .

Hi,

We are using portingset 6.1c.07.13 otherwise you cannot install Baan IV on SQL Server 2005.

Thanks Alexander

Is this a problem with all dates in all session. Is it for migrated data or new data or both . What is the SQL2k5 SP .

Hi All,

I have the following problem:
I am working on a UNIX to Windows migration and after the initial installation and transfer of Tools environment the following errors occur
In any Baan IV session whenever a date is inserted or updated we get an error 205 form the system telling hte value is out of range.
The Windows Event log says the following

Env baan (c:\baan)
Prog msql7 file \MSQL\msql_data.c # 769
Keyword Date out of range
Username baan type S language 1
Process 0x1734
Lasterror 997 (Overlapped I/O operation is in progress.)
Errno 0
bdberrno 0
Message
dbs_errno = 205, Error 205 occurred:
bshell date -2147483648 (-2147483648 days) is not supported. The valid supported range of dates are from 02/01/1753 (639907 days) to 31/12/9999 (3652059 days) [dd/mm/yyyy].
DBMS Input: Data out of range for R_GTEQ on dbo.ttdsls038003.
Flushed at \MSQL\msql_row.c : #244.

Is there anybody out here that knows why a wrong date is sent to the database.
An other point is that when I enter a record via ttaad4100 in a table this DOES work and no errors occur.

Any advise is appreciated

Hi all,

Yesterday I have solved the problem, the tabledef6.1 file did not contain the MSQL_LEVEL1=0 parameter and that caused the problems. Thanks to all for your help

Alexander