Re: NLS_DATE_FORMAT not working on PC

While that is true, any 'windowing' date handling is a bit of a kludge and restricts you to 2 centuries for dates ( OK, so that's not a problem for most users) - If you have a large number of apps that were written to use 2 digit years this may be the only solution until the apps are redone ( and most apps should be redone periodically - the period depends on the app ) ( scripts can be modified more easily with a grep-like tool and could be redone more quickly)

No future apps should allow the entry of 2 digit years and then the full 4 digit year date format can be used.

Just my 2c

BBruce_at_Erols.com wrote:

>Use 'DD-MON-RR' and you will still be able to use 2 digit years and
>not wreck all of your scripts and confuse your users.
>
>Brad
>
>On Mon, 10 Jan 2000 14:50:32 GMT, johng_at_mm.com (TurkBear) wrote:
>
>>On the nT clients use regedit and look at
>>HKEY_LOCAL_MACHINE..Software..Oracle
>>and check the entry for NLS_DATE_FORMAT - set it to the 'DD-MON-YYYY' format (
>>or any format with a 4 digit year you want )
>>
>>If there is no NLS_DATE_FORMAT, add it and set it as above...
>>
>>Hope it helps..
>>
>>Note: Registry editing can be dangerous--you may want to have a tech support
>>person do it for you....
>>
>>
>>Karen <bko00_at_my-deja.com> wrote:
>>
>>>In article <852h2r$26t$1_at_nnrp1.deja.com>,
>>> alistair.thomson_at_sphinxcst.co.uk wrote:
>>>> Yep the client settings override the server settings! Try adding the
>>>> nls entry into the registry on the client and all should be well.
>>>>
>>>> In article <851qu7$i16$1_at_nnrp1.deja.com>,
>>>> mbraund_at_my-deja.com wrote:
>>>> > I have an Oracle V7 database with nls_date_format parameter set
>>>> to 'DD-
>>>> > MON-RR'.
>>>> >
>>>> > When accessing the database through the Solaris SQL*Plus application
>>>> > this behaves as expected :
>>>> >
>>>> > 01-DEC-99 is stored as 01-DEC-1999
>>>> > 01-JAN-00 is stored as 01-JAN-2000
>>>> >
>>>> > When accessing the same database with the same userid through the PC
>>>> > SQL*Plus client through SQL Net I get the following :
>>>> >
>>>> > 01-DEC-99 is stored as 01-DEC-2099
>>>> > 01-JAN-00 is stored as 01-JAN-2000
>>>> >
>>>> > Selecting from nls_session_parameters reveals NLS_DATE_FORMAT = 'DD-
>>>> MON-
>>>> > YY' while selecting from nls_instance_parameters reveals
>>>> > NLS_DATE_FORMAT = 'DD-MON-RR'
>>>> >
>>>> > Doing an explicit ALTER SESSION to set the nls_date_format yields
>>>the
>>>> > correct results.
>>>> >
>>>> > Why is the PC access not working by default ? Is the database
>>>> parameter
>>>> > being overridden ?
>>>> >
>>>> > Sent via Deja.com http://www.deja.com/
>>>> > Before you buy.
>>>> >
>>>>
>>>> Sent via Deja.com http://www.deja.com/
>>>> Before you buy.
>>>>
>>>
>>>Can you tell me how to do that?
>>>We found the same problem, using NT connecting to both
>>>Solaris and SCO Openserver platforms (against 8.0.6 and 7.2)
>>>
>>>Thanks!
>>>Karen
>>>
>>>
>>>Sent via Deja.com http://www.deja.com/
>>>Before you buy.
>>
>>
>>
>> -----------== Posted via Newsfeeds.Com, Uncensored Usenet News ==----------
>> http://www.newsfeeds.com The Largest Usenet Servers in the World!
>>------== Over 73,000 Newsgroups - Including Dedicated Binaries Servers ==-----

  -----------== Posted via Newsfeeds.Com, Uncensored Usenet News ==----------    http://www.newsfeeds.com The Largest Usenet Servers in the World! ------== Over 73,000 Newsgroups - Including Dedicated Binaries Servers ==----- Received on Tue Jan 11 2000 - 08:57:55 CST