Link to home
Start Free TrialLog in
Avatar of Gary_Brown_Applied
Gary_Brown_Applied

asked on

Using keyboard only, how do I move to the next Rich Text Field

Hi All,

I have a database with a lot of documents in it, the form that these documents use has four rich text fields in it.
I need to access each of these RTF fields and change some formatting.
I am planning to do this using Macro Scheduler (a keyboard macro program).
The problem I am having is figuring out how to get into the next Rich Text Field, using keyboard commands only.
I know that to move between normal field you press the TAB key, but once in a RTF then TAB indents the text, not moves to the next field.
The RTF field content varies in length, so it is not a simple matter of pressing the down arrow four times

Any suggestions on what key combinations will allow me 'programatically' to move to the next RTF will be gratefully received.

Regards,
Gary.
ASKER CERTIFIED SOLUTION
Avatar of CRAK
CRAK
Flag of Netherlands image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Isn't it possible to program the changes you want to make to the documents using the programming facilities of Notes??
Avatar of HemanthaKumar
HemanthaKumar

If you are using R6.. There is a property for the richtext field (check contro tab) to specify tab action should move focus to next field. R5 doesn't support this !

~Hemanth
One way around it would be for your keymacro program to call an agent that does [EditGotoField].
Avatar of Gary_Brown_Applied

ASKER

Thanks CRAK.

The way I have got this to work is to create a new form (based off the old one) with the field settings as you suggested.

I am going to open the document, switch the form, do my editing and then switch the form back to the original.
Hemanth,
I can't check in R6 right now (I wish they would finally get me off R5 and into R6.5 here at office), but the "Pressing tab key moves to next field" property actually is availavle in R5!

Gary_Brown_Applied,
Thanks for the points. As an alternative approach for the 2nd form you might consider a computed subform, based on @ClientType and @IsDocBeingEdited.