Path: newssvr20.news.prodigy.com!newsmst01.news.prodigy.com!prodigy.com!rip!sjc70.webusenet.com!news.webusenet.com!pd7cy2so!pd7cy1no!shaw.ca!sn-xit-03!sn-xit-04!sn-xit-01!sn-post-02!sn-post-01!supernews.com!corp.supernews.com!not-for-mail From: Sybrand Bakker Newsgroups: comp.databases.oracle.server Subject: Re: TO_CHAR function & client machine local configuration Date: Tue, 11 Nov 2003 20:14:09 +0100 Organization: Posted via Supernews, http://www.supernews.com Message-ID: <55d2rv0jpv89rf15m6lfpfm7403pr83dqq@4ax.com> Sender: Sybrand Bakker Reply-To: Sybrand Bakker References: X-Newsreader: Forte Agent 1.93/32.576 English (American) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Complaints-To: abuse@supernews.com Lines: 17 Xref: newssvr20.news.prodigy.com comp.databases.oracle.server:247457 On Tue, 11 Nov 2003 18:01:14 +0100, "Jon" wrote: >when using the followin function: TO_CHAR(SYSDATE, 'DY') or TO_CHAR(SYSDATE, >'D'), depending the client machine from which I run the function, the result >changes. Can I use any function that could give me universally the same >result, not depending on the local configuration of the client machine but >the server configuration. Thanks > a) you can include the NLS_DATE_FORMAT in the to_char function b) Microsux supports connecting to a network registry *and* locking the PC, so end-users can't change the registry c) create an on-logon trigger that sets the proper format. -- Sybrand Bakker, Senior Oracle DBA