Thank you, I will do that.... Regards, Desmond
On 6 March 2015 at 15:53, Tracy Pearson <[email protected]> wrote: > Desmond Lloyd wrote on 2015-03-06: > > First thanks for the response I got yesterday on what I presented as a > Tab > > Order problem. > > > > Am running a VP6 form from a real old FoxPro accounting system. It has > a > > bunch of menu generation overhead and these huge procedure files... On > one > > of their screens which is handwritten with says and gets I call this > > form. it is modeless, default show window, with a read events > > statement after the do myform statement. Form works fine however, > after > > clicking on the edit button I set focus to one of the controls, if I tab > > out of it the cursor progresses to the next control, if I use the > mouse > I > > can progress to the next control. However pressing enter always > executes > > the buttons click event! > > > > Thought that was strange so I checked the behavior on another form > (called > > from another button on the malfunctioning button). Exact same scenario, > > but after setting focus on the control I can successfully press enter > and > > move to the next.... > > > > So I wrote a quick test form with three text boxes and executed roughly > the > > same code in a button on that form. Executed the from the same place > and > > once again I could successfully move from control to control using the > > enter button. > > > > The problem I have with pressing the enter key and having the click fire > is > > that the user could save something prematurely and then will have to > click > > the edit button to finish their edits. > > > > I apologize for my long "windedness" , but am totally baffled why it > works > > on every other form, except this one? BTW I even rebuilt the form > > (copying the contents of my methods) and no joy? > > > > Does anyone have any ideas? > > Regards, > > Desmond > > > > Desmond, > > I had one of those @Say forms in one of our projects. When we tested things > in Windows Vista, that form had a lot of display issues. > > That aside, You have a test form that behaves as you expect. > This rebuilt form where you've copied all the code from the suspect form, > still has the problem. > > You can get the THISFORM.ActiveObject.Name property to determine what > control really has focus. I would probably put that in a Wait Window in the > Form.Activate event. > > Tracy Pearson > PowerChurch Software > > [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/CAAJXvaP6PFShWQbCS_outjmUC_RzR1=iaq1ge4a64t6d1e1...@mail.gmail.com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
