Re: NLS_DATE_FORMAT & W95 Doesn't Work

[Quoted] As you wish to use a 4 digit year the RR option is of no use to you (and it doesn't seem to work in Forms anyway)
Message 1843 is 'not a valid month' so it would appear that Oracle is expecting something like 'AUG' instead of '08' which would be correct for tha AMERICAN NLS_LANG setting.
The NLS_DATE_FORMAT parameter IS the one to use. Try using TOOL_ENV.GETVAR procedure to query the setting at runtime. This is documented in the Procedure Builder Devleloper's Guide and a small form built around this can be quite useful in debugging your applications.

[Quoted] D. Scott Moyer, Jr. <dmoyer_at_gpu.com> wrote in article <32c7da18.6860736_at_internet.gpuc.com>...
>
> Our date format is required to be mm/dd/yyyy or rrrr to
> facilitate user input. Under W3.1 we would just remove the NLS_LANG
> parameter from the ORACLE.INI file and not include the NLS_DATE_FORMAT
> parameter and queries and data retrieval worked OK. We are now
> converting to W95 and nothing seems to work the same. The registry
> has the NLS_LANG parameter as AMERICAN_AMERICA.WE8ISO885P1. With or
> without the NLS_DATE_FORMAT set to MM/DD/RR, I keep receiving the
> invalid month error 1843 when I query for date '08/08/96' for example.
> Our server side has the NLS_DATE_FORMAT set to MM/DD/RR also. Server
> side queries work fine with whatever date format we set.
>
> So how do I get our date format to work for all applications?
> (DES2K, DEV2K, DIS2K, SQLPLUS) Please post reply or email responses
> to dmoyer_at_gpu.com.
>
> TIA
>
> d scott moyer jr
> dmoyer_at_gpu.com (work)
> dsmoyer_at_enter.net (home)
>
Received on Wed Jan 01 1997 - 00:00:00 CET