On Sep 14, 2009, at 8:41 AM, Allen wrote:
> level form. I called it "MyToolbar"
> Create your top level form and give it a property "oToolbar"
> Set the classlib in form.init to your class library
> In activate createobject("thisform.otoolbar","mytoolbar")
I did something similar in my VFP framework. (And, "no" you don't
have to do a formset.) I have one toolbar that is an alternative to
the "main" application menu that launches the most-used forms, and a
second toolbar that handles simple navigation and searching. YOu just
use the form-control class to coordinate the content. So it is a
single toolbar with VCR buttons, a combobox to choose the current
index, a search capability (which calls my generic search screen,
which works without regard to the current table and index). So as the
user moves from screen to screen, the toolbar changes to reflect the
options available for *that* screen.
Nice to get that stuff off of a screen, and that a user has a single
place to look for navigation no matter what else he has on the screen.
Ken
_______________________________________________
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/356f1544-a656-43bc-9ca8-f4e972f7c...@information-architecture.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.
