Re: Oracle Report for Windows ported to UNIX error
Date: 16 Jul 1998 05:31:27 GMT
Message-ID: <6ok37f$q8h$1_at_inet16.us.oracle.com>
In article <35ADC287.F555BDE2_at_profit.maginfo.net>,
Dmitry G. Bezgodov <dima_at_profit.maginfo.net> wrote:
] josephxu_at_my-dejanews.com wrote:
]
] > REP-3300: Fatal error in Toolkit II (UI).
] > UI-9: This function call is out of context.
]
] I guess You need to set a few useful variables, for example,
] see part of my .profile:
Note that these are all sh(1) settings ("NAME=value;export NAME"). For csh(1), it'd be "setenv NAME value".
] PRINTER = lj5 # Real printer name from /etc/printcap (BSD Style)
This one most Unix folks have set already. (Do make sure it's set for you.)
] TK2_PRINT = "lpr -P'%n' -#%c -h" # BSD Print style
This is only necessary if you need BSD printing on a non-BSD Unix box. (Or vice versa--then you'd set it to "lp...".)
Again, only if the default printer status command is the wrong way 'round for your installation. (For BSD sites, it should really be set to "lpc status %n"; setting it to "echo" just turns off printer checking.)
] NLS_LANG = AMERICAN_AMERICA.US7ASCII # Set your native charset
This is the default on most installations already; you'd need to set it only if the default isn't right for you.
The real kicker, though, is to properly configure your ?/tk/admin/uiprint.txt file for the printers you've got available. (It's a text file--the documentation is at the top of the file.)
- Bill K.
Bill Kaufman, | "Patience is a virtue. Seersucker is a fabric." wkaufman_at_us.oracle.com | -- Bazooka Joe(Required text follows) The statements and opinions expressed here are my own and do not necessarily represent those of Oracle Corporation. Received on Thu Jul 16 1998 - 07:31:27 CEST