| Subject |
Re: versatility of the Inspector |
| From |
Alex Safian <noway@noway.com> |
| Date |
Tue, 27 Oct 2020 23:16:27 -0400 |
| Newsgroups |
dbase.getting-started |
Forgot the period! Should be Msxml2.XMLHttp
Alex Safian Wrote:
> It's mentioned in Ken's books too. One place it's very useful is if you're using oleAutoClient to establish a connection to an outside program (like Word or Excel) or even Msxml2XMLHttp . Instantiate it in the command window with objHttp = new oleAutoClient("Msxml2XMLHttp") and then inspect it and you can see the events, methods and properties (which dBase gets from the registry). With this you can use web services in a desktop app.
>
> Gaetano Wrote:
>
> >
> > Hi All,
> >
> > While looking at a Help entry recently I realized that the Inspector is
> > not only available in the designers but also as a standalone command -
> > inspect(<object>) - that can be used with any object even during program
> > execution apparently.
> >
> > I had never heard anyone suggest to use Inspect(), it may be that
> > everyone knows this and uses it or that it is one of the little known
> > features of dBase.
> >
> > I have many time thought about how to get to know all the available
> > properties or events of an object, especially after someone on the NG's
> > told me about a property I had no idea existed, and this seems to be the
> > answer to it.
> >
> > I tried it on the command line on the _app object and it returned an
> > inspection window with a variety of info like the character set, iniFile
> > location, currentUserPath...etc., including a custom property that I had
> > just created to check if it would be listed.
> >
> > So is anyone using this regularly? and if so, in what context do you
> > find it useful?
> >
> > Cheers,
> > Gaetano.
> >
> >
> >
>
|
|