No. However - that would seem to defeat the purpose of that Visible
command. I want the main FoxPro screen NOT to be visible when my utility
is running. 
 
-K-

-----Original Message-----
From: [email protected] [mailto:[email protected]]
On Behalf Of Grigore Dolghin
Sent: Wednesday, October 06, 2010 12:20 PM

Have you tried to put the read events after _Screen.Visible = .T.?

> -----Original Message-----
> From: [email protected] [mailto:profoxtech-
> [email protected]] On Behalf Of Kurt Wendt
> Sent: Wednesday, October 06, 2010 7:12 PM
> To: [email protected]
> Subject: RE: A Problem w/My Focus!
> 
> Hi Tracy - thanks for the follow-up!
> 
> To answer your questions/suggestions.
> 
> Yes - I repeatedly checked and confirmed setting of the Tab Order to 1
for
> this item.
> 
> As for the TextBox - it actually has NO ControlSource set for it, and
its
> definitely enabled.
> 
> I have the Read Events code in the calling program - which is the Main
prog of
> the Project. That code looks as such:
>       _screen.visible = .F.
>       DO FORM main_scan
>       READ EVENTS
>       _screen.visible = .T.
> 
> It almost looks like the Form itself is the one that is not getting
the Focus -
> based upon a little experimentation I was just doing now...
> 
> -K-
> 
> 
> -----Original Message-----
> From: [email protected] [mailto:profoxtech-
> [email protected]]
> On Behalf Of Tracy Pearson
> Sent: Wednesday, October 06, 2010 11:54 AM
> 
> 
> Kurt Wendt wrote on 2010-10-06:
> > I am working on this small Utility/Project for one of our clients -
> > which will be used at a Warehouse. Almost ALL user interactions will
> be
> > done via a BarCode scanner. They will be scanning UCC barcodes on
> boxes
> > - and then the UPC barcodes for the contents within the boxes.
> >
> > I even included a SetFocus command for the TextBox within the
Activate
> > Method of the Form - but, that still does NOT solve the problem!
> >
> >
> 
> Kurt,
> 
> If the textbox is not enabled, which can happen when the controlsource
is a
> readonly field in a cursor, you might get this behavior.
> 
> Make sure the textbox is the lowest number in the tab order of the
parent
> container. Make sure it's parent container (if not the form directly)
is also the
> lowest number.
> 
> Where's the Read Events command? Sometimes this can take focus off the
> form.
> 
> Tracy Pearson
> PowerChurch Software

_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: 
http://leafe.com/archives/byMID/profox/289ea162f5642645b5cf64d624c66a14071a2...@us-ny-mail-002.waitex.net
** 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.

Reply via email to