D3 and mvBase

Hi all

I reside in the UK and for our "sins" we still honor the European data format of DD/MM/YYYY.

There is a conversion code which 'e'  which according to the D3 manual states:

This is great, however, I discovered something rather disturbing and am wondering whether anyone (this side of the Atlantic) can see (a) if I'm doing something wrong OR (b) has uncovered this.

BTW - I am aware of the set-date-eur option in a coldstart - which (in my case) I have not opted to have.

See this code:

*My_Date = '30/09/2022'
*crt My_Date
b_date = '19997'
crt b_date
c = Oconv(b_date, 'D4/E')
crt c
crt 'next '
d = Iconv(c, 'D4/E')
crt d
crt ' and Done!'

The results are as follows:

19997
30/09/2022
next

and Done!

Which is "disturbing" as the Iconv resolves to a NULL date!

Any ideas (please)

Thanks

Stefano

Hi all

I reside in the UK and for our "sins" we still honor the European data format of DD/MM/YYYY.

There is a conversion code which 'e'  which according to the D3 manual states:

This is great, however, I discovered something rather disturbing and am wondering whether anyone (this side of the Atlantic) can see (a) if I'm doing something wrong OR (b) has uncovered this.

BTW - I am aware of the set-date-eur option in a coldstart - which (in my case) I have not opted to have.

See this code:

*My_Date = '30/09/2022'
*crt My_Date
b_date = '19997'
crt b_date
c = Oconv(b_date, 'D4/E')
crt c
crt 'next '
d = Iconv(c, 'D4/E')
crt d
crt ' and Done!'

The results are as follows:

19997
30/09/2022
next

and Done!

Which is "disturbing" as the Iconv resolves to a NULL date!

Any ideas (please)

Thanks

Stefano

Hi all

I reside in the UK and for our "sins" we still honor the European data format of DD/MM/YYYY.

There is a conversion code which 'e'  which according to the D3 manual states:

This is great, however, I discovered something rather disturbing and am wondering whether anyone (this side of the Atlantic) can see (a) if I'm doing something wrong OR (b) has uncovered this.

BTW - I am aware of the set-date-eur option in a coldstart - which (in my case) I have not opted to have.

See this code:

*My_Date = '30/09/2022'
*crt My_Date
b_date = '19997'
crt b_date
c = Oconv(b_date, 'D4/E')
crt c
crt 'next '
d = Iconv(c, 'D4/E')
crt d
crt ' and Done!'

The results are as follows:

19997
30/09/2022
next

and Done!

Which is "disturbing" as the Iconv resolves to a NULL date!

Any ideas (please)

Thanks

Stefano

Hi all

I reside in the UK and for our "sins" we still honor the European data format of DD/MM/YYYY.

There is a conversion code which 'e'  which according to the D3 manual states:

This is great, however, I discovered something rather disturbing and am wondering whether anyone (this side of the Atlantic) can see (a) if I'm doing something wrong OR (b) has uncovered this.

BTW - I am aware of the set-date-eur option in a coldstart - which (in my case) I have not opted to have.

See this code:

*My_Date = '30/09/2022'
*crt My_Date
b_date = '19997'
crt b_date
c = Oconv(b_date, 'D4/E')
crt c
crt 'next '
d = Iconv(c, 'D4/E')
crt d
crt ' and Done!'

The results are as follows:

19997
30/09/2022
next

and Done!

Which is "disturbing" as the Iconv resolves to a NULL date!

Any ideas (please)

Thanks

Stefano

Hi all

I reside in the UK and for our "sins" we still honor the European data format of DD/MM/YYYY.

There is a conversion code which 'e'  which according to the D3 manual states:

This is great, however, I discovered something rather disturbing and am wondering whether anyone (this side of the Atlantic) can see (a) if I'm doing something wrong OR (b) has uncovered this.

BTW - I am aware of the set-date-eur option in a coldstart - which (in my case) I have not opted to have.

See this code:

*My_Date = '30/09/2022'
*crt My_Date
b_date = '19997'
crt b_date
c = Oconv(b_date, 'D4/E')
crt c
crt 'next '
d = Iconv(c, 'D4/E')
crt d
crt ' and Done!'

The results are as follows:

19997
30/09/2022
next

and Done!

Which is "disturbing" as the Iconv resolves to a NULL date!

Any ideas (please)

Thanks

Stefano

Hi all

I reside in the UK and for our "sins" we still honor the European data format of DD/MM/YYYY.

There is a conversion code which 'e'  which according to the D3 manual states:

This is great, however, I discovered something rather disturbing and am wondering whether anyone (this side of the Atlantic) can see (a) if I'm doing something wrong OR (b) has uncovered this.

BTW - I am aware of the set-date-eur option in a coldstart - which (in my case) I have not opted to have.

See this code:

*My_Date = '30/09/2022'
*crt My_Date
b_date = '19997'
crt b_date
c = Oconv(b_date, 'D4/E')
crt c
crt 'next '
d = Iconv(c, 'D4/E')
crt d
crt ' and Done!'

The results are as follows:

19997
30/09/2022
next

and Done!

Which is "disturbing" as the Iconv resolves to a NULL date!

Any ideas (please)

Thanks

Stefano

Hy i use the statement 

SET-DATE-EUR

in my logon macro of the account.. so all my dates are convert to this format and also inside programs

*My_Date = '30/09/2022'*crt My_Datecrt 'Now Eurpoean'EXECUTE 'set-date-eur'   ;* Europeanb_date = '19997'crt b_datec = Oconv(b_date, 'D4/')crt ccrt 'next 'd = Iconv(c, 'D4/')crt dcrt 'Now American'EXECUTE 'set-date-std'   ;* Americanb_date = '19997'crt b_datec = Oconv(b_date, 'D4/')crt ccrt 'next 'd = Iconv(c, 'D4/')crt dcrt ' and Done!'

https://www3.rocketsoftware.com/rocketd3/support/documentation/d3nt/102/refman/TCL/set_date_eur_command.htm#reference5811

Hi all

I reside in the UK and for our "sins" we still honor the European data format of DD/MM/YYYY.

There is a conversion code which 'e'  which according to the D3 manual states:

This is great, however, I discovered something rather disturbing and am wondering whether anyone (this side of the Atlantic) can see (a) if I'm doing something wrong OR (b) has uncovered this.

BTW - I am aware of the set-date-eur option in a coldstart - which (in my case) I have not opted to have.

See this code:

*My_Date = '30/09/2022'
*crt My_Date
b_date = '19997'
crt b_date
c = Oconv(b_date, 'D4/E')
crt c
crt 'next '
d = Iconv(c, 'D4/E')
crt d
crt ' and Done!'

The results are as follows:

19997
30/09/2022
next

and Done!

Which is "disturbing" as the Iconv resolves to a NULL date!

Any ideas (please)

Thanks

Stefano

Hi Alberto,

Yes thanks, aware of the set-date-eur line in coldstart.
I was just (disturbed) that the ICONV would not return a valid date when I JUST OCONV the (valid) date.

Brian explained why and all's good thanks :)

It's just something a developer needs to be made aware of when (and if) you receive an Excel spreadsheet with a date (assume here 'dd/mm/yyyy') and good practice is to ICONV said date.

This is how I came about this "issue" - no set-date-eur in coldstart - date looks good until you ICONV and OCONV it back with 'D4/E' - and surprise surprise it's NULL

[Per my test example:]

But thanks :)

b_date = '19997'
crt b_date
c = Oconv(b_date, 'D4/E')
crt c
crt 'next '
d = Iconv(c, 'D4/E')
crt d
crt ' and Done!'

Hy i use the statement 

SET-DATE-EUR

in my logon macro of the account.. so all my dates are convert to this format and also inside programs

*My_Date = '30/09/2022'*crt My_Datecrt 'Now Eurpoean'EXECUTE 'set-date-eur'   ;* Europeanb_date = '19997'crt b_datec = Oconv(b_date, 'D4/')crt ccrt 'next 'd = Iconv(c, 'D4/')crt dcrt 'Now American'EXECUTE 'set-date-std'   ;* Americanb_date = '19997'crt b_datec = Oconv(b_date, 'D4/')crt ccrt 'next 'd = Iconv(c, 'D4/')crt dcrt ' and Done!'

https://www3.rocketsoftware.com/rocketd3/support/documentation/d3nt/102/refman/TCL/set_date_eur_command.htm#reference5811

Hi all

I reside in the UK and for our "sins" we still honor the European data format of DD/MM/YYYY.

There is a conversion code which 'e'  which according to the D3 manual states:

This is great, however, I discovered something rather disturbing and am wondering whether anyone (this side of the Atlantic) can see (a) if I'm doing something wrong OR (b) has uncovered this.

BTW - I am aware of the set-date-eur option in a coldstart - which (in my case) I have not opted to have.

See this code:

*My_Date = '30/09/2022'
*crt My_Date
b_date = '19997'
crt b_date
c = Oconv(b_date, 'D4/E')
crt c
crt 'next '
d = Iconv(c, 'D4/E')
crt d
crt ' and Done!'

The results are as follows:

19997
30/09/2022
next

and Done!

Which is "disturbing" as the Iconv resolves to a NULL date!

Any ideas (please)

Thanks

Stefano

Hy Stefano... 

my first awnser as incomplete...

then i editid 
  alternative you can use

*My_Date = '30/09/2022'*crt My_Datecrt 'Now Eurpoean'EXECUTE 'set-date-eur'   ;* Europeanb_date = '19997'crt b_datec = Oconv(b_date, 'D4/')crt ccrt 'next 'd = Iconv(c, 'D4/')crt dcrt 'Now American'EXECUTE 'set-date-std'   ;* Americanb_date = '19997'crt b_datec = Oconv(b_date, 'D4/')crt ccrt 'next 'd = Iconv(c, 'D4/')crt dcrt ' and Done!'

Hi Alberto,

Yes thanks, aware of the set-date-eur line in coldstart.
I was just (disturbed) that the ICONV would not return a valid date when I JUST OCONV the (valid) date.

Brian explained why and all's good thanks :)

It's just something a developer needs to be made aware of when (and if) you receive an Excel spreadsheet with a date (assume here 'dd/mm/yyyy') and good practice is to ICONV said date.

This is how I came about this "issue" - no set-date-eur in coldstart - date looks good until you ICONV and OCONV it back with 'D4/E' - and surprise surprise it's NULL

[Per my test example:]

But thanks :)

b_date = '19997'
crt b_date
c = Oconv(b_date, 'D4/E')
crt c
crt 'next '
d = Iconv(c, 'D4/E')
crt d
crt ' and Done!'

Hy i use the statement 

SET-DATE-EUR

in my logon macro of the account.. so all my dates are convert to this format and also inside programs

*My_Date = '30/09/2022'*crt My_Datecrt 'Now Eurpoean'EXECUTE 'set-date-eur'   ;* Europeanb_date = '19997'crt b_datec = Oconv(b_date, 'D4/')crt ccrt 'next 'd = Iconv(c, 'D4/')crt dcrt 'Now American'EXECUTE 'set-date-std'   ;* Americanb_date = '19997'crt b_datec = Oconv(b_date, 'D4/')crt ccrt 'next 'd = Iconv(c, 'D4/')crt dcrt ' and Done!'

https://www3.rocketsoftware.com/rocketd3/support/documentation/d3nt/102/refman/TCL/set_date_eur_command.htm#reference5811

Hi all

I reside in the UK and for our "sins" we still honor the European data format of DD/MM/YYYY.

There is a conversion code which 'e'  which according to the D3 manual states:

This is great, however, I discovered something rather disturbing and am wondering whether anyone (this side of the Atlantic) can see (a) if I'm doing something wrong OR (b) has uncovered this.

BTW - I am aware of the set-date-eur option in a coldstart - which (in my case) I have not opted to have.

See this code:

*My_Date = '30/09/2022'
*crt My_Date
b_date = '19997'
crt b_date
c = Oconv(b_date, 'D4/E')
crt c
crt 'next '
d = Iconv(c, 'D4/E')
crt d
crt ' and Done!'

The results are as follows:

19997
30/09/2022
next

and Done!

Which is "disturbing" as the Iconv resolves to a NULL date!

Any ideas (please)

Thanks

Stefano

you can do something like this

PROGRAM CONVERTDATE  (DATE$CON)
DATE   = FIELD(DATE$CON,"/",1)

MONTH = FIELD(DATE$CON,"/",2)

YEAR = FIELD(DATE$CON,"/",3)

DATE$CON = MONTH:"/"DATE:"/":YEAR

EXECUTE 'SET-DATE-STD'

DATE$CON = ICONV(DATE$CON,"D4/")

RETURN

-----------------------------------------------

DATE$E = "13/10/2022" ;* EUROPEAN DATE

DATA$AMERICAN = ICONV(DATE$,"CALL CONVERTDATE)

------------------------------
Alberto Leal
System Analyst
Millano Distribuidora de Auto Pecas Ltda
Varzea Grande MT BR

Original Message:
Sent: 10-13-2022 10:05
From: Alberto Leal
Subject: European Date format

Hy Stefano... 

my first awnser as incomplete...

then i editid 
  alternative you can use

*My_Date = '30/09/2022'*crt My_Datecrt 'Now Eurpoean'EXECUTE 'set-date-eur'   ;* Europeanb_date = '19997'crt b_datec = Oconv(b_date, 'D4/')crt ccrt 'next 'd = Iconv(c, 'D4/')crt dcrt 'Now American'EXECUTE 'set-date-std'   ;* Americanb_date = '19997'crt b_datec = Oconv(b_date, 'D4/')crt ccrt 'next 'd = Iconv(c, 'D4/')crt dcrt ' and Done!'

Hi Alberto,

Yes thanks, aware of the set-date-eur line in coldstart.
I was just (disturbed) that the ICONV would not return a valid date when I JUST OCONV the (valid) date.

Brian explained why and all's good thanks :)

It's just something a developer needs to be made aware of when (and if) you receive an Excel spreadsheet with a date (assume here 'dd/mm/yyyy') and good practice is to ICONV said date.

This is how I came about this "issue" - no set-date-eur in coldstart - date looks good until you ICONV and OCONV it back with 'D4/E' - and surprise surprise it's NULL

[Per my test example:]

But thanks :)

b_date = '19997'
crt b_date
c = Oconv(b_date, 'D4/E')
crt c
crt 'next '
d = Iconv(c, 'D4/E')
crt d
crt ' and Done!'

Hy i use the statement 

SET-DATE-EUR

in my logon macro of the account.. so all my dates are convert to this format and also inside programs

*My_Date = '30/09/2022'*crt My_Datecrt 'Now Eurpoean'EXECUTE 'set-date-eur'   ;* Europeanb_date = '19997'crt b_datec = Oconv(b_date, 'D4/')crt ccrt 'next 'd = Iconv(c, 'D4/')crt dcrt 'Now American'EXECUTE 'set-date-std'   ;* Americanb_date = '19997'crt b_datec = Oconv(b_date, 'D4/')crt ccrt 'next 'd = Iconv(c, 'D4/')crt dcrt ' and Done!'

https://www3.rocketsoftware.com/rocketd3/support/documentation/d3nt/102/refman/TCL/set_date_eur_command.htm#reference5811

Hi all

I reside in the UK and for our "sins" we still honor the European data format of DD/MM/YYYY.

There is a conversion code which 'e'  which according to the D3 manual states:

This is great, however, I discovered something rather disturbing and am wondering whether anyone (this side of the Atlantic) can see (a) if I'm doing something wrong OR (b) has uncovered this.

BTW - I am aware of the set-date-eur option in a coldstart - which (in my case) I have not opted to have.

See this code:

*My_Date = '30/09/2022'
*crt My_Date
b_date = '19997'
crt b_date
c = Oconv(b_date, 'D4/E')
crt c
crt 'next '
d = Iconv(c, 'D4/E')
crt d
crt ' and Done!'

The results are as follows:

19997
30/09/2022
next

and Done!

Which is "disturbing" as the Iconv resolves to a NULL date!

Any ideas (please)

Thanks

Stefano