Re: HELP!: Keyboard Mapping and SQL*Forms + dialing in
Date: Tue, 9 Mar 1993 19:55:25 GMT
Message-ID: <1993Mar9.195525.17950_at_dxcern.cern.ch>
In article <Mar.8.12.25.53.1993.13746_at_andromeda.rutgers.edu>, holowcza_at_andromeda.rutgers.edu (Richard D Holowczak) writes:
>
> Hi Folks:
>
> We're running Oracle on a Sun Sparcserver. When I dial in
> using CrossTalk or Procomm Plus for Windows on my PC, I have
> no problems using the VT220 or VT320 terminal emulators.
>
> Problem is, most of the people who need to access SQL*Forms
> are dialing in with software that only supports VT100 or VT102
> terminals. Also, we use NCSA Telnet which also emulates a
> VT102 terminal. Most of the software tested does not have
> all of the function key mappings needed to design forms.
>
> For example, under the "Key Help" screen, SQL*Forms suggests
> we press the "Do" key or ^O to Accept or Commit. There is no
> "Do" key mapping and ^O has no effect.
>
> What are people using when dialing in out there?
>
>
> Thanks
>
> Rich Holowczak holowcza_at_andromeda.rutgers.edu
Hi!
By default, SQL*Forms will use a vt220 mapping ( at least in VAX/VMS environment ), so if you work with a vt100 or vt102 , you should use the -c switch to tell forms to work with the proper mapping.
sqlforms -c vt100 user/passwd
Hope it helps.
Have nice day! Received on Tue Mar 09 1993 - 20:55:25 CET