Global App Object

[Alan Gillott]

One of the items that currently annoys me is the lack of a Global APP
Object. The current APP object is local to the executable: EXE or DLL not to
the executing APP. For some of the functions this is OK but in other
circumstances this is a pesky nuisance. For example if I have a DLL called
by an EXE I want to have available at least:

APP.APPEXEName
APP.APPPath
APP.APPStartmode
APP.APPTitle

I also understand that this a little more complex when the top of the chain
is on another m/c or is a Web function. In that case, what is the global
app. I would be interested in suggested definitions that can be forwarded to
MS as a group request.

Thanks

[Stephen Johsnon]

"Alan Gillott" <agillott@tact.com> wrote:
>One of the items that currently annoys me is the lack of a Global APP
>Object. The current APP object is local to the executable: EXE or DLL not
to
>the executing APP. For some of the functions this is OK but in other
>circumstances this is a pesky nuisance. For example if I have a DLL called
>by an EXE I want to have available at least:
>
>APP.APPEXEName
>APP.APPPath
>APP.APPStartmode
>APP.APPTitle
>
>I also understand that this a little more complex when the top of the chain
>is on another m/c or is a Web function. In that case, what is the global
>app. I would be interested in suggested definitions that can be forwarded
to
>MS as a group request.
>
>Thanks
>
>
The method that I have used in my Dll's is to pass a reference to the APP
object to the DLL (Property, Method, whatever). The DLL then can access
the executable's APP object information just like the Executable can. This
method works well.

[Alan Gillott]

I know that but having to do so is a pain, especially if you have no control
over your caller.

Stephen Johsnon <sjohnson@pplinc.com> wrote in message
news:38d27f8c$1@news.devx.com...
>
> "Alan Gillott" <agillott@tact.com> wrote:
> >One of the items that currently annoys me is the lack of a Global APP
> >Object. The current APP object is local to the executable: EXE or DLL not
> to
> >the executing APP. For some of the functions this is OK but in other
> >circumstances this is a pesky nuisance. For example if I have a DLL
called
> >by an EXE I want to have available at least:
> >
> >APP.APPEXEName
> >APP.APPPath
> >APP.APPStartmode
> >APP.APPTitle
> >
> >I also understand that this a little more complex when the top of the
chain
> >is on another m/c or is a Web function. In that case, what is the global
> >app. I would be interested in suggested definitions that can be forwarded
> to
> >MS as a group request.
> >
> >Thanks
> >
> >
> The method that I have used in my Dll's is to pass a reference to the APP
> object to the DLL (Property, Method, whatever). The DLL then can access
> the executable's APP object information just like the Executable can.
This
> method works well.
>