All of the APIs (UV ones, at least) have the same quirk/feature...once you know (usually found out the hard way), you just need to have your own initialise routine to setup everything.
Regards, David -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Adrian Matthews Sent: Tuesday, 17 August 2004 8:42 AM To: [EMAIL PROTECTED] Subject: RE: [U2] Quirk of Uniobjects? On all our VB code (which we no longer use) we did an explicit DATE.FORMAT from the uniobjects session as the login is bypassed for those sessions. ________________________________ From: [EMAIL PROTECTED] on behalf of Simon Carter Sent: Mon 16/08/2004 15:28 To: [EMAIL PROTECTED] Subject: [U2] Quirk of Uniobjects? 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. ------- u2-users mailing list [EMAIL PROTECTED] To unsubscribe please visit http://listserver.u2ug.org/
