Thinking about this more, I am not sure (will try it asap) if changing the
login procedure will do the trick because the login procedure will likely
run as part of the connect..

--
-anil
Research and Development, Query Processing
iAnywhere Solutions Engineering

-------------------------------------------------------------------------
** Whitepapers, TechDocs, bug fixes are all available through the **
** iAnywhere Developer Community at http://www.ianywhere.com/developer **
-------------------------------------------------------------------------

"anil k goel" <firstname.no-junk.lastname@spam.ianywhere.com> wrote in
message news:...
> The block of code in your request log below that is setting
> timestamp_format, etc. is coming from the ODBC driver. The driver sets
> these options to the standard ODBC values right after connecting.
>
> If you want to override these standard values, you can do so in your
> application or by changing the login procedure.
>
> --
> -anil
> Research and Development, Query Processing
> iAnywhere Solutions Engineering
>
> -------------------------------------------------------------------------
> ** Whitepapers, TechDocs, bug fixes are all available through the **
> ** iAnywhere Developer Community at http://www.ianywhere.com/developer **
> -------------------------------------------------------------------------
>
> <Mike Allen> wrote in message news:424ace56.5d29.1681692777@sybase.com...
>> Turned logging on and sure enough it is getting changed by
>> the second command executed after the connect. The
>> connection is coming from an ODBC client. I have no code
>> written to do this. Is this part of an internal Procedure?
>> My first SQL does not occur until 5 to 8 statements later.
>> Where are these statements coming from?
>>
>>
>>
>> I. 03/30 10:40:37. ** CONNECT conn: 2 UID=cms_app
>> I. 03/30 10:40:37. ** DONE conn: 2 CONNECT
>> Conn=2
>> I. 03/30 10:40:37. ** REQUEST conn: 2 STMT_PREPARE
>> "SELECT @@version, if 'A'<>'a' then 1 else 0 endif, if
>> db_property('IsIQ') = 'YES' then 1 else 0 endif"
>> I. 03/30 10:40:37. ** DONE conn: 2 STMT_PREPARE
>> Stmt=65536
>> I. 03/30 10:40:37. ** REQUEST conn: 2 STMT_EXECUTE
>> Stmt=-1
>> I. 03/30 10:40:37. ** DONE conn: 2 STMT_EXECUTE
>> I. 03/30 10:40:37. ** REQUEST conn: 2 STMT_DROP
>> Stmt=65536
>> I. 03/30 10:40:37. ** DONE conn: 2 STMT_DROP
>> I. 03/30 10:40:37. ** REQUEST conn: 2 STMT_PREPARE
>> "SET TEMPORARY OPTION Time_format = 'hh:nn:ss';SET
>> TEMPORARY OPTION Timestamp_format = 'yyyy-mm-dd
>> hh:nn:ss.ssssss';SET TEMPORARY OPTION Date_format =
>> 'yyyy-mm-dd';SET TEMPORARY OPTION Date_order = 'ymd';SET
>> TEMPORARY OPTION Isolation_level = 0;"
>> I. 03/30 10:40:37. ** DONE conn: 2 STMT_PREPARE
>> Stmt=65537
>> I. 03/30 10:40:37. ** REQUEST conn: 2 STMT_EXECUTE
>> Stmt=-1
>> I. 03/30 10:40:37. ** DONE conn: 2 STMT_EXECUTE
>>> Is the client changing that value transparently?
>>>
>>> Run a Request level log (-zr sql )to see if the option is
>>> being reset.
>>>
>>>
>>> <Mike Allen> wrote in message
>>> news:424abfd6.5bb7.1681692777@sybase.com... >I am trying
>>> > to change the Date_order option for the database.
>>> > I have set option public.date_order = MDY
>>> > I have set the same option for the user's logon
>>> > and still when the user logs on the option is set to the
>>> > default YMD
>>> > I am running ASA9.0.2 on a WIN2003 box.
>>> > What am I missing here?
>>>
>>>
>
>