Viewing Objects as Tabs instead of a Sidebar

[TitansFan]

I know this seems trivial but in access 97, in Database view, the objects (Tables, Forms, Reports, etc.) were shown across the top of the database box as Tabs. In Access 2000 and later, they are shown down the left side in a sidebar. Is there any way in A2K or later to have those objects showns as Tabs again across the top? It was much more user-friendly and easier to navigate. I am aware of the Shortcut Bar but that's not what I'm looking for. Thanks

Stu Miller

 

[Van T. Dinh]

I don't think there is any way, AFAIK. Microsoft decided
to change the GUI of Access to be more "in-line" with
other applications.

Another point to note is that users (at least users of
databases I develop) don't normally see the Database
Containers window, anyway. Generally, users should be
using Forms for activities in the database where you (as
the developer) can code to control and validate the users'
actions.

HTH
Van T. Dinh
MVP (Access)

-----Original Message-----
I know this seems trivial but in access 97, in Database

view, the objects (Tables, Forms, Reports, etc.) were
shown across the top of the database box as Tabs. In
Access 2000 and later, they are shown down the left side
in a sidebar. Is there any way in A2K or later to have
those objects showns as Tabs again across the top? It was
much more user-friendly and easier to navigate. I am
aware of the Shortcut Bar but that's not what I'm looking
for. Thanks.

 

[TitansFan]

Thanks, Van. I was afraid that was the answer. Our users have the ability to deal with the Tables, Forms, and Reports. Unusual, I know, but they are pretty talented. They do not, however, change the design at any time.
Stu

 

[Brendan Reynolds]

The Access <version> Developers Handbook (where '<version>' might be 97,
2000, or 2002) by Ken Getz et all, published by Sybex, has an example of how
to use a form as a custom database window. If the feature is important
enough to justify the effort, you might be able to modify that example to
meet your needs.

--
Brendan Reynolds (MVP)

Thanks, Van. I was afraid that was the answer. Our users have the

ability to deal with the Tables, Forms, and Reports. Unusual, I know, but
they are pretty talented. They do not, however, change the design at any
time.

 

[Rick Brandt]

The Access <version> Developers Handbook (where '<version>' might be 97,
2000, or 2002) by Ken Getz et all, published by Sybex, has an example of how
to use a form as a custom database window. If the feature is important
enough to justify the effort, you might be able to modify that example to
meet your needs.

I've been using my own DB Window now for about two years. I hardly ever
look at the built in one except for simple apps with a small number of
objects. Once you get used to the possible customizations with your own
form, the built in one feels really inadequate.

 

[Dirk Goldgar]

I've been using my own DB Window now for about two years. I hardly
ever look at the built in one except for simple apps with a small
number of objects. Once you get used to the possible customizations
with your own form, the built in one feels really inadequate.

Out of curiosity, Rick, what sort of customizations have you
implemented?

 

[Rick Brandt]

Out of curiosity, Rick, what sort of customizations have you
implemented?

Well the one I find most useful might not be helpful to anyone who uses a
different naming convention. In my one "large" app I have all of the object
names prefixed by the functional category (all objects for the Rec/Insp area are
prefixed 'rc' etc..). I have a ListBox with all of the possible prefixes and
when I select one the object list is filtered so I only see the matching
objects. That really helps when there are lots of objects.

I also put in options that make copying and renaming possible with fewer clicks
and keystrokes, functions to automatically do SaveAsText and other things like
that. I'm using a ListBox for the object list so obviously I have only one
column, but I actually find that a narrow, but tall object form is less
obtrusive anyway. I made it a popup so if I want I can slide it over onto my
second monitor which is also nice.

 

[Dirk Goldgar]

Well the one I find most useful might not be helpful to anyone who
uses a different naming convention. In my one "large" app I have all
of the object names prefixed by the functional category (all objects
for the Rec/Insp area are prefixed 'rc' etc..). I have a ListBox
with all of the possible prefixes and when I select one the object
list is filtered so I only see the matching objects. That really
helps when there are lots of objects.

I also put in options that make copying and renaming possible with
fewer clicks and keystrokes, functions to automatically do SaveAsText
and other things like that. I'm using a ListBox for the object list
so obviously I have only one column, but I actually find that a
narrow, but tall object form is less obtrusive anyway. I made it a
popup so if I want I can slide it over onto my second monitor which
is also nice.

Interesting ideas, Rick. Thanks for sharing them.

 

[Van T. Dinh]

In AXP, I just create functional Groups in the Groups section of the list on
the left of the Database Containers window and add shortcuts of Access
Objects to different functional groups.

But the idea of the AccessObject Form where you can move it to the second
monitor is certainly useful.