Re: Using VB app to show Excel?

From: Jim Carlock (anonymous_at_127.0.0.1)
Date: 05/07/04 

Date: Fri, 7 May 2004 13:21:39 -0400

I'm slowly going through the thread here, and I can see where
a timer in the VB app can check at certain intervals to see if the
Excel app is open, provided the VB prog opened the Excel
App... I haven't made it to the end yet... so just tossing a
cookie out to all to grab it and do something with it. 

-- 
Jim Carlock
http://www.microcosmotalk.com/
Post replies to the newsgroup.
"Karl E. Peterson" <karl@mvps.org> wrote in message
news:%235p08KtMEHA.2388@TK2MSFTNGP09.phx.gbl...
Ed <Ed_Millis@NOSPAM.Hotmail.com> wrote:
>> There really isn't another way, other than to test on the lowest-level
>> system you intend to support.  After awhile, you'll become familiar with
>> what's causing issues and what isn't.  Then, you gamble, if it's not
>> critical.  If it is, well, you test.
>>
>> I keep a Win95 box around for just this purpose, as well as an NT4 server
I
>> can "get to" via pcAnywhere.  You oughta be able to scrounge up hardward
>> like that almost for free these days.
>
> Unfortunately, Karl, I do know what's causing the issues - my XP-level VBA
> codes are looking for XP-level DLLs on lower-level systems.  Since they
> don't exist, my users get odd and confusing (to them) error messages, when
> it worked fine the week before!
  Guy says to doctor, "Doc, it hurts when I do this..."
  Doc says, "Don't *do* that!"
What are "XP-level DLLs" and why are you messing with them?  VBA is very
portable.
> Given the fact that my job (a peon with a
> contractor for the government) does not include *any* level of programming
> (although I've stretched myself into that arena and many are glad for it),
> I'm not entitled to that kind of support.  They allow me to do what I do
now
> only because it has helped me do my regular job (technical writer) and
also
> helped others, but without interfering with my regular duties or asking
too
> much for support my job position isn't supposed to require.
Well, I can certainly appreciate that position.  It's a very common one in
the VB(A)
world.  Doesn't change the reality of the situation you're in, though.
> Back to square one - I'm stuck.  Have I mapped out a workable (if not the
> best and most reasonable) way to get unstuck?  I figure if I can't get the
> Workbook_Close to unload the VB app, I can at least pop up a BIG FORM
saying
> "Click the "exit" button on the toolbar."
Okay, now you're talking about stuff that isn't clear to me.  I do think
folks here
can help.  But a more complete picture is required.  In particular, if you
can
isolate the problem to just what's causing the pain, we may have ideas on
other ways
to do it.
Later...   Karl
-- 
[Microsoft Basic: 1976-2001, RIP]