Hey All-

I don't think this is possible, but we'd love it if it were.

We would like to have a pane of our own design docked along the left
side of our Access application's main window. This pane might have any
number of things on it... buttons, a treeview, etc... and have a layout
we would specify. It would need to be truly docked to the main window,
like a toolbar is, and be resizable. (Some of the things we've found
for doing this are just controls that go onto an Access form--not
acceptable in this implementation.)

We can't find anything that does this. Any ideas? It's ok if the
implementation is non-trivial (windows api, subclassing, creating an
ocx).

Thanks,
-Tom

Could you accomplish your purpose with a main form that included the
functionality you describe, and show all your other Forms embedded in a
Subform Control. It'd be a matter of resetting the SourceObject of the
Subform Control.

Larry Linson
Microsoft Access MVP

"TD" <tom.darci@gmail.com> wrote in message
news:1138061387.150612.49100@g49g2000cwa.googlegro ups.com...[color=blue]
> Hey All-
>
> I don't think this is possible, but we'd love it if it were.
>
> We would like to have a pane of our own design docked along the left
> side of our Access application's main window. This pane might have any
> number of things on it... buttons, a treeview, etc... and have a layout
> we would specify. It would need to be truly docked to the main window,
> like a toolbar is, and be resizable. (Some of the things we've found
> for doing this are just controls that go onto an Access form--not
> acceptable in this implementation.)
>
> We can't find anything that does this. Any ideas? It's ok if the
> implementation is non-trivial (windows api, subclassing, creating an
> ocx).
>
> Thanks,
> -Tom
>[/color]

Hi Larry,
Thanks for the reply. Unfortunately, having a main form with a
subform control as a container for everything in the application isn't
a very attractive option to us. Some of the things that are stopping us
from going that way are:

* Reports can't appear in that container
* We would like the look and feel of a true pane, where the user can
resize its width in a native Windows sort of way.
* Since subforms can only be nested 3-deep, you burn up one of those
with the container layer, effectively giving you just 2-deep.

-Tom

Check out www.componentsource.com. You might call them.

--
PC Datasheet
Your Resource For Help With Access, Excel And Word Applications
Over 1100 users have come to me from the newsgroups requesting help
resource@pcdatasheet.com



"TD" <tom.darci@gmail.com> wrote in message
news:1138061387.150612.49100@g49g2000cwa.googlegro ups.com...[color=blue]
> Hey All-
>
> I don't think this is possible, but we'd love it if it were.
>
> We would like to have a pane of our own design docked along the left
> side of our Access application's main window. This pane might have any
> number of things on it... buttons, a treeview, etc... and have a layout
> we would specify. It would need to be truly docked to the main window,
> like a toolbar is, and be resizable. (Some of the things we've found
> for doing this are just controls that go onto an Access form--not
> acceptable in this implementation.)
>
> We can't find anything that does this. Any ideas? It's ok if the
> implementation is non-trivial (windows api, subclassing, creating an
> ocx).
>
> Thanks,
> -Tom
>[/color]

"TD" <tom.darci@gmail.com> wrote in
news:1138123534.947786.228160@z14g2000cwz.googlegr oups.com:
[color=blue]
> Thanks for the reply. Unfortunately, having a main form with a
> subform control as a container for everything in the application
> isn't a very attractive option to us. Some of the things that are
> stopping us from going that way are:
>
> * Reports can't appear in that container
> * We would like the look and feel of a true pane, where the user
> can
> resize its width in a native Windows sort of way.
> * Since subforms can only be nested 3-deep, you burn up one of
> those
> with the container layer, effectively giving you just 2-deep.[/color]

What about resizing all your objects, forms, reports, etc., to fit
the available space? There's a form resizing class module on the
Access Web that I've used, and it has an example of how to figure
out the size of the Access client window so you can fit a form into
it. If you wanted to fit several forms in it, you could definitely
do that, as well.

I'm not certain if you can resize and position reports in that way,
though. Unfortunately, it seems that forms can be used in reports,
but not vice versa.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/

To the original poster:

Most people here have a common belief that the newsgroups are for *free
exchange of information*.
But Steve is a notorious job hunter in these groups, always trying to sell
his services.


Before you intend to do business with him look at:
http://home.tiscali.nl/arracom/whoissteve.html (updated)



"PC Datasheet" <nospam@nospam.spam> wrote in message
news:qFvBf.4838$rH5.1442@newsread2.news.atl.earthl ink.net...[color=blue]
> Check out www.componentsource.com. You might call them.
>
> --
> PC Datasheet
> Your Resource For Help With Access, Excel And Word Applications
> Over 1100 users have come to me from the newsgroups requesting[/color]
help[color=blue]
> resource@pcdatasheet.com
>
>
>
> "TD" <tom.darci@gmail.com> wrote in message
> news:1138061387.150612.49100@g49g2000cwa.googlegro ups.com...[color=green]
> > Hey All-
> >
> > I don't think this is possible, but we'd love it if it were.
> >
> > We would like to have a pane of our own design docked along the left
> > side of our Access application's main window. This pane might have any
> > number of things on it... buttons, a treeview, etc... and have a layout
> > we would specify. It would need to be truly docked to the main window,
> > like a toolbar is, and be resizable. (Some of the things we've found
> > for doing this are just controls that go onto an Access form--not
> > acceptable in this implementation.)
> >
> > We can't find anything that does this. Any ideas? It's ok if the
> > implementation is non-trivial (windows api, subclassing, creating an
> > ocx).
> >
> > Thanks,
> > -Tom
> >[/color]
>
>[/color]