Thanks Mike... and Javier.
Works like a charm.
Dick Fey
----- Original Message ----- From: "MikeB" <[EMAIL PROTECTED]>
To: "RBG7-L Mailing List" <[EMAIL PROTECTED]>
Sent: Saturday, December 11, 2004 2:34 PM
Subject: [RBG7-L] - Re: Fw: [RBG7-L] - Re: A new pony
Ok, I just tested this and you are supposed to put the Skip 1 in the Button
Eep, because the last edit still has focus and the skip 1actually executes in
that field. But the caveat is for the Skip 1 to work, there has to be a field
or something after the last edit to Skip to, so you might have to put a
variable edit box after the last field and set its width to 0 to hide it... If
you want to remember you did this, don't set the width to 0 in design mode, set
it to 5 or so and give it a component id and set it to 0 in the form onAfter
load eep.
Try that.. It worked here.
Sorry for the confusion..
----- Original Message ----- From: "Dick Fey" <[EMAIL PROTECTED]>
To: "RBG7-L Mailing List" <[EMAIL PROTECTED]>
Sent: Saturday, December 11, 2004 3:03 PM
Subject: [RBG7-L] - Fw: [RBG7-L] - Re: A new pony
Mike: That is my point...They will not exit that field at all, therefore an
exit eep does not do it. They just enter info into the second field, then
click on the speed button 'exit'.
They think they have exit-ed the field, but Rbase does not. So the second
variable is not saved.
Dick
Subject: [RBG7-L] - Re: A new pony
>
>
>> Scratch the list box. Did it a different way.
>>
>> New problem...
>>
>> I have a small form with 2 variable fields, and a speed button to >> exit.
>>
>> I like the speed button because I can make it invisible, just a nice >> text
>> item 'EXIT' that does not look like a button.
>>
>> If you make entries into the fields then hit the speed button, >> obviously
>> the
>> second field does not save because you didn't really exit it, even >> though
>> it
>> will appear to a user that they did. To save it, you actually have to
>> hit
>> tab or enter which of course throws you back into the first field.
>
>> I am sure users will NOT remember to do that
>>
>> I cannot seem to find a way in an eep to force the second field to >> save
>> without actually exiting it as above.
>
>>From a couple of weeks back.. JWA (Javiers' Work Around)
>
> put
>
> Skip 1
>
> into the last editbox onExit eep to force the Save..
>
>
>> I know I can use any button IN the tab order that would force a save.
>>
>> So it seems to me that we need a button that IS in the tab order that >> we
>> could make invisible.
>> God knows we have enough buttons, we should be able to give one of >> them
>> that
>> option.
>>
>> Any other suggestions?
>>
>> But boy it is coming along.... and it is beautiful.
>>
>> Thanks to those of you have helped me get where I am with it.
>>
>> Dick Fey
>> Carpet Broker Inc.
>>
>
>
>
>
