Thanks

This did the trick.

Bjorn 

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Brian Leach
Sent: 16 August 2004 06:27
To: [EMAIL PROTECTED]
Subject: RE: [U2] Quirk of Uniobjects?

Remember,

UniObjects does not run any LOGIN or similar initialisation stuff, including
wherever you set your DATE.FORMAT. You need to explicitly run this as part
of your connection script.

NOTE that on some installations, I've found that it disappears if you call
it from an execute in a subroutine, and you need to explicitly run it from
the COMMAND object. 

Duh.

Regards,

Brian 

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: 16 August 2004 16:26
To: [EMAIL PROTECTED]
Subject: Re: [U2] Quirk of Uniobjects?

Simon,

do you not use an explicit conversion code when you ICONV, e.g
"D/DMY[2,2,2]" for "dd/mm/yy"?

John Appleyard
Arthur J. Gallagher (UK) Limited




 

                      "Simon Carter"

                      <[EMAIL PROTECTED]         To:
<[EMAIL PROTECTED]>                                           
                      CO.UK>                          cc:      (bcc: John
Appleyard/BSDUK/AJG)                                          
                      Sent by:                        Subject: [U2] Quirk of
Uniobjects?                                                
                      [EMAIL PROTECTED]

                      er.u2ug.org

 

 

                      16/08/2004 15:28

                      Please respond to

                      u2-users

 

 





Hello all,

Has anyone else found the following, or am I missing something obvious here?

I've been working on some VB6 code running uniobjects (v5.2, as is the
version of Unidata/NT), and had the need to pass a date out to a unibasic
subroutine called via the subroutine object. Said subroutine does a little
bobbing about with the passed date, and then constructs a further date (sort
of day:"/":month:"/":year construct), which is then ICONVed and returned to
the VB program. The problem that I found was the the ICONV in the databasic
returned an internal date as though the originally constructed date was in
MM/DD/YY (American) format, although being in the UK we use the European
DD/MM/YY format, as specified in the DATE.FORMAT verb (on the server, and
also executed as part of the login).

Is this correct? Have I missed something?

Thanks for any replies.



Simon Carter
-------
u2-users mailing list
[EMAIL PROTECTED]
To unsubscribe please visit http://listserver.u2ug.org/

________________________________________________________________________
This email was checked by MessageLabs SkyScan before entering Microgen.


________________________________________________________________________
This email was checked on leaving Microgen for viruses, similar malicious
code and inappropriate content by MessageLabs SkyScan.

DISCLAIMER

This email and any attachments are confidential and may also be privileged.

If you are not the named recipient, please notify the sender immediately and
do not disclose the contents to any other person, use it for any purpose, or
store or copy the information.

In the event of any technical difficulty with this email, please contact the
sender or [EMAIL PROTECTED]

Microgen Information Management Solutions http://www.microgen.co.uk
-------
u2-users mailing list
[EMAIL PROTECTED]
To unsubscribe please visit http://listserver.u2ug.org/
-------
u2-users mailing list
[EMAIL PROTECTED]
To unsubscribe please visit http://listserver.u2ug.org/

Reply via email to