The ctrl-tab keystroke can be used to tab out of edit tables. But ctrl-tab doesn't seem to work in a child window run from a frame. When I run the same child window alone ctrl-tab works all right.

Could somebody verify this? And suggest a fix or workaround?

- Oystein -

Try Ctrl-Enter - it works much better!

Robert

Robert,

I didn't know that. Ctrl-Enter does tab out of edit tables, also in MDI context.

But there might be problems with Ctrl-Enter in windows with a "default button". I did an experiment and both Enter and Ctrl-Enter triggered the default button.

But in the Popup window it's different again. If the edit table of the Popup window has focus, Ctrl-Enter does nothing at all.

I still do wish Ctrl-Tab would work. I try to keep my clients from using Enter to get to the next field. Tab is in general so much safer. If they now have to use Ctrl-Enter in edit tables it's more likely they'll use Enter elsewhere.

Btw - I also tried Ctrl-Tab and Ctrl-Enter in some other controls than edit tables. After all users might sometimes do the wrong keystroke when they have to switch between several ones. Mostly nothing happened, but I discovered that in edit boxes Ctrl-Tab inserts a tab character, and Ctrl-Enter is exactly like Enter ([i]newline).

Thanks a lot! I do appreciate your reply, even if I realize it might not sound so!

- Oystein -

Ours is not to reason why. Ours is but to do and die!

I didn't know that Ctrl-Enter also fired the default button because I tend to use a save button (icon of a floppy disk) accelerated with F9 for saving data entry screens without setting that as a default button. I try and only use OK buttons for non-database associated collector screens but some of those do have multiple edittables so your point is valid. There is therefore no way of using the keyboard to move from one to the other whilst having a default button set.

Perhaps Revelation could look at stopping Ctrl-Enter firing the default button in a future upgrade?

View this thread on the forum...