Problems while using ingres form based commands

This is a discussion on Problems while using ingres form based commands within the Ingres Database forums in Other Databases category; I am facing problems while using ingres form based commands. I have tried following things. 1. I have set TERM_INGRES to vt100f . But the problem in this case is numpad keys are not mapped, so I am not been able to use corresponding options requiring numpad keys. But when I am accessing the serever on which ingres database resides from putty , it works fine. 2. I have set TERM_INGRES to vt220 and TERM to xterm In this case, it is not finding any key mappings such as F13 to F20 Keys. So beacuse of this I am not been able ...

Go Back   Database Forum > Other Databases > Ingres Database

Database Forums

Register FAQ Calendar Search Today's Posts Mark Forums Read
  #1  
Old 08-04-2005, 09:36 PM
Default Problems while using ingres form based commands

I am facing problems while using ingres form based commands.
I have tried following things.

1. I have set "TERM_INGRES" to "vt100f".
But the problem in this case is numpad keys are not mapped, so I
am not been able to use
corresponding options requiring numpad keys.
But when I am accessing the serever on which ingres database
resides from "putty", it works
fine.
2. I have set "TERM_INGRES" to "vt220" and "TERM" to "xterm"
In this case, it is not finding any key mappings such as F13 to
F20 Keys. So beacuse of this I
am not been able to use those command options.

Another problem is since Laptop does not have the numpad, i will have
to map all the respective key options corresponding to numpad to left
side keys on the keyboad.
Since it is not getting respective key mappings, so I request if any
one is having solution on this,please do let me know.

Regards,
- Ajay

--
Posted using the http://www.dbforumz.com interface, at author's request
Articles individually checked for conformance to usenet standards
Topic URL: http://www.dbforumz.com/Ingres-Probl...ict244574.html
Visit Topic URL to contact author (reg. req'd). Report abuse: http://www.dbforumz.com/eform.php?p=849192
Reply With Quote
  #2  
Old 08-05-2005, 09:30 AM
Default Re: Problems while using ingres form based commands

another option that i never see mentioned (from too far back in ancient
days, i suspect) but that i always use when sitting at an unfamiliar
keyboard/terminal emulator is simply setting TERM_INGRES=vt100
function key usage disappears altogether. you use the ESC key to get the
cursor down to the menu line (and to cycle the menu line if necessary)
and you simple type in the first couple distinguishing characters of the
option you want and hit Return. a heck of a lot easier than messing with
mappings...

cb


Ajay wrote:
> I am facing problems while using ingres form based commands.
> I have tried following things.
>
> 1. I have set "TERM_INGRES" to "vt100f".
> But the problem in this case is numpad keys are not mapped, so I
> am not been able to use
> corresponding options requiring numpad keys.
> But when I am accessing the serever on which ingres database
> resides from "putty", it works
> fine.
> 2. I have set "TERM_INGRES" to "vt220" and "TERM" to "xterm"
> In this case, it is not finding any key mappings such as F13 to
> F20 Keys. So beacuse of this I
> am not been able to use those command options.
>
> Another problem is since Laptop does not have the numpad, i will have
> to map all the respective key options corresponding to numpad to left
> side keys on the keyboad.
> Since it is not getting respective key mappings, so I request if any
> one is having solution on this,please do let me know.
>
> Regards,
> - Ajay
>

Reply With Quote
Reply


Thread Tools
Display Modes



All times are GMT -4. The time now is 10:53 PM.


Powered by vBulletin® Version 3.6.8
Copyright ©2000 - 2009, Jelsoft Enterprises Ltd.
Integrated by bbpixel2009 :: jvbPlugin R1013.368.1

Search Engine Friendly URLs by vBSEO 3.1.0
vB Ad Management by =RedTyger=
In an effort to better serve ads to our visitors, cookies are used on Mydatabasesupport.com. For more information, check out our Privacy Policy.