Parse VB/VBA Code

[Steve Jorgensen]

Re: Parse VB/VBA Code

On Tue, 14 Oct 2003 20:02:59 GMT, dXXXfenton@bway .net.invalid (David W.
Fenton) wrote:
[color=blue]
>nospam@nospam. nospam (Steve Jorgensen) wrote in
><huvnov8vnfu5m rb7jkgq833o90q4 eh4ume@4ax.com> :
>[color=green]
>>I'm not familliar with any free hosing[/color]
>
>I'll hose your code from free, Steve.[/color]

D.F.,

I really can't tell what your message is trying to say, but It's addressed
to me. Clarify?

[TC]

Re: Parse VB/VBA Code


"Steve Jorgensen" <nospam@nospam. nospam> wrote in message
news:28mlov8kq7 cp5g0neo5ep7rae r3r7v5mgq@4ax.c om...[color=blue]
> I have just done some research on this subject, and it turns out that to[/color]
do[color=blue]
> it right, you need to buy a license for VBA integration. This is the only
> way to get the DLLs that give you access to the same information that
> AutoSense has. Without that, you can theoretically do what you want (as
> you have started to do), but it's up to you to pares everything correctly
> such determining as what's a comment (snip)[/color]


Steve, I thougt that VBA Integration was the process of taking your own
application - written in any language, storing data in any format - and
exposing its capabilities as objects, methods and properties that can be
used by any VBA client. Then, for example, you could automate your
application from any Office program. That is not what the OP is doing?

As for intellisense, I'm a bit out of my league here, but I think that the
data comes directly from the relevant type libraries (.tlb files or
whatever). I believe there are documented APIs for reading those files. So
it is just a metter of writing appropriate code, to get that data out.

Yes? No?

TC

[Steve Jorgensen]

Re: Parse VB/VBA Code

On Wed, 15 Oct 2003 13:48:31 +1200, "TC" <a@b.c.d> wrote:
[color=blue]
>
>"Steve Jorgensen" <nospam@nospam. nospam> wrote in message
>news:28mlov8kq 7cp5g0neo5ep7ra er3r7v5mgq@4ax. com...[color=green]
>> I have just done some research on this subject, and it turns out that to[/color]
>do[color=green]
>> it right, you need to buy a license for VBA integration. This is the only
>> way to get the DLLs that give you access to the same information that
>> AutoSense has. Without that, you can theoretically do what you want (as
>> you have started to do), but it's up to you to pares everything correctly
>> such determining as what's a comment (snip)[/color]
>
>
>Steve, I thougt that VBA Integration was the process of taking your own
>application - written in any language, storing data in any format - and
>exposing its capabilities as objects, methods and properties that can be
>used by any VBA client. Then, for example, you could automate your
>application from any Office program. That is not what the OP is doing?[/color]

There is a VBA integration license that gives you the files and licenses to
be able to integrate the VBA engine directly into your program just like
Access or Word does. Rather than just exposing objects in an OLE/ActiveX
compatible way for access by VB/VBA code running elsewhere, you actually
host the VBA platform from within the application. From what I can tell,
if you want access to the low-level information like what the VBE has with
autosense, you need the files that are only available with the purchase of
this license.
[color=blue]
>As for intellisense, I'm a bit out of my league here, but I think that the
>data comes directly from the relevant type libraries (.tlb files or
>whatever). I believe there are documented APIs for reading those files. So
>it is just a metter of writing appropriate code, to get that data out.
>
>Yes? No?[/color]

Almost. The data comes from a TLB-like structure, but a VBA project has no
TLB file to read data from. You can use Tlbinf32.dll to get the
InterfaceInfo object from an instance of an object wonce you have an
instance created in a running VBA program, and that's been very useful to
be in some odd cases, but that's as far as I've been able to get with this
approach.

I'll try to post a link back in this thread soon to a VBA unit tester I
wrote that makes use of the InterfaceInfo I spoke of in the preceding
paragraph.
[color=blue]
>
>TC
>
>[/color]

[David W. Fenton]

Re: Parse VB/VBA Code

nospam@nospam.n ospam (Steve Jorgensen) wrote in
<qabpovs73k2el5 gvqjsac0iptrhid pas6a@4ax.com>:
[color=blue]
>On Tue, 14 Oct 2003 20:02:59 GMT, dXXXfenton@bway .net.invalid
>(David W. Fenton) wrote:
>[color=green]
>>nospam@nospam .nospam (Steve Jorgensen) wrote in
>><huvnov8vnfu5 mrb7jkgq833o90q 4eh4ume@4ax.com >:
>>[color=darkred]
>>>I'm not familliar with any free hosing[/color]
>>
>>I'll hose your code from free, Steve.[/color]
>
>D.F.,
>
>I really can't tell what your message is trying to say, but It's
>addressed to me. Clarify?[/color]

It's just a bad joke, based on your typo of "hosing" when you meant
"hosting."

<Emily Litella>
Never mind.
</Emily Litella>

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc

[R. Soul]

Re: Parse VB/VBA Code


"David W. Fenton" <dXXXfenton@bwa y.net.invalid> wrote in message
news:94157F178d fentonbwaynetin vali@24.168.128 .90...[color=blue]
> nospam@nospam.n ospam (Steve Jorgensen) wrote in
> <qabpovs73k2el5 gvqjsac0iptrhid pas6a@4ax.com>:
>[color=green]
> >On Tue, 14 Oct 2003 20:02:59 GMT, dXXXfenton@bway .net.invalid
> >(David W. Fenton) wrote:
> >[color=darkred]
> >>nospam@nospam .nospam (Steve Jorgensen) wrote in
> >><huvnov8vnfu5 mrb7jkgq833o90q 4eh4ume@4ax.com >:
> >>
> >>>I'm not familliar with any free hosing
> >>
> >>I'll hose your code from free, Steve.[/color]
> >
> >D.F.,
> >
> >I really can't tell what your message is trying to say, but It's
> >addressed to me. Clarify?[/color]
>
> It's just a bad joke, based on your typo of "hosing" when you meant
> "hosting."
>
> <Emily Litella>
> Never mind.
> </Emily Litella>
>
> --
> David W. Fenton http://www.bway.net/~dfenton
> dfenton at bway dot net http://www.bway.net/~dfassoc[/color]



If you remember Steve Jorgensen's Joke of the Day feature from a while back,
you will not be surprised to find he didn't get it. Have a look here:

http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&oe=UTF-8&q=%22Steve+Jorgensen%22+programmer+humor&sa=N&tab=wg

[Steve Jorgensen]

Re: Parse VB/VBA Code

On Wed, 15 Oct 2003 15:16:39 GMT, dXXXfenton@bway .net.invalid (David W.
Fenton) wrote:
[color=blue]
>nospam@nospam. nospam (Steve Jorgensen) wrote in
><qabpovs73k2el 5gvqjsac0iptrhi dpas6a@4ax.com> :
>[color=green]
>>On Tue, 14 Oct 2003 20:02:59 GMT, dXXXfenton@bway .net.invalid
>>(David W. Fenton) wrote:
>>[color=darkred]
>>>nospam@nospa m.nospam (Steve Jorgensen) wrote in
>>><huvnov8vnfu 5mrb7jkgq833o90 q4eh4ume@4ax.co m>:
>>>
>>>>I'm not familliar with any free hosing
>>>
>>>I'll hose your code from free, Steve.[/color]
>>
>>D.F.,
>>
>>I really can't tell what your message is trying to say, but It's
>>addressed to me. Clarify?[/color]
>
>It's just a bad joke, based on your typo of "hosing" when you meant
>"hosting."[/color]

Thanks for clearing that up - I was confused. It would have been more
clear with "" around "hose" :)

[rkc]

Re: Parse VB/VBA Code


"R. Soul" <soul@rest.co m> wrote in message
news:bmjp6a$t05 $1@hercules.bti nternet.com...[color=blue]
>
> "David W. Fenton" <dXXXfenton@bwa y.net.invalid> wrote in message
> news:94157F178d fentonbwaynetin vali@24.168.128 .90...[color=green]
> > nospam@nospam.n ospam (Steve Jorgensen) wrote in
> > <qabpovs73k2el5 gvqjsac0iptrhid pas6a@4ax.com>:
> >[color=darkred]
> > >On Tue, 14 Oct 2003 20:02:59 GMT, dXXXfenton@bway .net.invalid
> > >(David W. Fenton) wrote:
> > >
> > >>nospam@nospam .nospam (Steve Jorgensen) wrote in
> > >><huvnov8vnfu5 mrb7jkgq833o90q 4eh4ume@4ax.com >:
> > >>
> > >>>I'm not familliar with any free hosing
> > >>
> > >>I'll hose your code from free, Steve.
> > >
> > >D.F.,
> > >
> > >I really can't tell what your message is trying to say, but It's
> > >addressed to me. Clarify?[/color]
> >
> > It's just a bad joke, based on your typo of "hosing" when you meant
> > "hosting."
> >
> > <Emily Litella>
> > Never mind.
> > </Emily Litella>
> >
> > --
> > David W. Fenton http://www.bway.net/~dfenton
> > dfenton at bway dot net http://www.bway.net/~dfassoc[/color]
>
>
>
> If you remember Steve Jorgensen's Joke of the Day feature from a while[/color]
back,[color=blue]
> you will not be surprised to find he didn't get it. Have a look here:[/color]

If you recall this thread you'll know why one would not expect to see D.W.
trying to be funny.

http://www.google.com/groups?q=+%22sense+of+humor%22+group:comp.databases.ms-access+author:David+author:W.+author:Fenton&hl=en&lr=&ie=UTF-8&oe=UTF-8&selm=9160959BFdfentonbwaynet%40news-server.nyc.rr.com&rnum=3

[TC]

Re: Parse VB/VBA Code

Thanks for the info.

TC


Steve Jorgensen <nospam@nospam. nospam> wrote in message
news:gejpov8pdj 8pcr7kuu7g13bv1 ii46dr2i3@4ax.c om...[color=blue]
> On Wed, 15 Oct 2003 13:48:31 +1200, "TC" <a@b.c.d> wrote:
>[color=green]
> >
> >"Steve Jorgensen" <nospam@nospam. nospam> wrote in message
> >news:28mlov8kq 7cp5g0neo5ep7ra er3r7v5mgq@4ax. com...[color=darkred]
> >> I have just done some research on this subject, and it turns out that[/color][/color][/color]
to[color=blue][color=green]
> >do[color=darkred]
> >> it right, you need to buy a license for VBA integration. This is the[/color][/color][/color]
only[color=blue][color=green][color=darkred]
> >> way to get the DLLs that give you access to the same information that
> >> AutoSense has. Without that, you can theoretically do what you want[/color][/color][/color]
(as[color=blue][color=green][color=darkred]
> >> you have started to do), but it's up to you to pares everything[/color][/color][/color]
correctly[color=blue][color=green][color=darkred]
> >> such determining as what's a comment (snip)[/color]
> >
> >
> >Steve, I thougt that VBA Integration was the process of taking your own
> >application - written in any language, storing data in any format - and
> >exposing its capabilities as objects, methods and properties that can be
> >used by any VBA client. Then, for example, you could automate your
> >application from any Office program. That is not what the OP is doing?[/color]
>
> There is a VBA integration license that gives you the files and licenses[/color]
to[color=blue]
> be able to integrate the VBA engine directly into your program just like
> Access or Word does. Rather than just exposing objects in an OLE/ActiveX
> compatible way for access by VB/VBA code running elsewhere, you actually
> host the VBA platform from within the application. From what I can tell,
> if you want access to the low-level information like what the VBE has with
> autosense, you need the files that are only available with the purchase of
> this license.
>[color=green]
> >As for intellisense, I'm a bit out of my league here, but I think that[/color][/color]
the[color=blue][color=green]
> >data comes directly from the relevant type libraries (.tlb files or
> >whatever). I believe there are documented APIs for reading those files.[/color][/color]
So[color=blue][color=green]
> >it is just a metter of writing appropriate code, to get that data out.
> >
> >Yes? No?[/color]
>
> Almost. The data comes from a TLB-like structure, but a VBA project has[/color]
no[color=blue]
> TLB file to read data from. You can use Tlbinf32.dll to get the
> InterfaceInfo object from an instance of an object wonce you have an
> instance created in a running VBA program, and that's been very useful to
> be in some odd cases, but that's as far as I've been able to get with this
> approach.
>
> I'll try to post a link back in this thread soon to a VBA unit tester I
> wrote that makes use of the InterfaceInfo I spoke of in the preceding
> paragraph.
>[color=green]
> >
> >TC
> >
> >[/color]
>[/color]