Prev: Unix timestamp to VB Date
Next: WebBrowser Control KeyPreview
From: Karl E. Peterson on 18 Dec 2009 14:10
on 12/18/2009, Steve supposed :
> I have tried adding quotes...no change in result.
>
> As far as the returned process ID...it is different each time I run
> (of coarse) but is alway similar to 4420 which is the value returned
> from my most recent attempt.

It's starting, alright. Just for kicks, you might try vbMaximized?
(Any chance it's just starting off-screen with vbNormal?)

--
..NET: It's About Trust!
http://vfred.mvps.org


From: Ralph on 18 Dec 2009 14:06

"Karl E. Peterson" <karl(a)exmvps.org> wrote in message
news:u$EAV8AgKHA.2184(a)TK2MSFTNGP04.phx.gbl...
> Steve explained on 12/18/2009 :
> > The code to launch the other app is just a simple
> > shell call (lngProcID = Shell(strAppPath)). The call to Shell does
> > return a value but the app does not appear to have been started (does
> > not show up visually and is not in task manager).
>
> What's the returned value? (If it's between 0-32, that indicates
> failure.)
>

Those failures are usually caught by the VB Error Handler. Thus - you have
an error before you can check the return. Might just as well read the
Err.Number. <g>

If invoking "cmd", either explicitly or implicitly, the return will often
indicate success - even after a VB Error has been caught, because the
DOSPrompt window launched correctly and you get the process ID for it.

-ralph


From: Steve on 18 Dec 2009 14:08
On Dec 18, 1:54 pm, "Nobody" <nob...(a)nobody.com> wrote:
> "Steve" <sredm...(a)yahoo.com> wrote in message
>
> news:81b5310d-6611-4b95-97ad-2271c2f6c213(a)k4g2000yqb.googlegroups.com...
>
> > Where can I find this app Process Explorer?
>
> Type "Process Explorer" in Google then click "I'm Feeling Lucky!"

Ok I found and installed Process Explorer and indeed the app is
starting then imediately terminating.
I wonder why this would be?
Again using the exact same string in the Run dialog starts the app as
expected.
I thought that calling shell from VB was essentialy indentical to
launching an app via the Run dialog.

?????

Thanks,
Steve
From: Karl E. Peterson on 18 Dec 2009 14:19
Steve expressed precisely :
> On Dec 18, 1:54�pm, "Nobody" <nob...(a)nobody.com> wrote:
>> "Steve" <sredm...(a)yahoo.com> wrote in message
>>
>> news:81b5310d-6611-4b95-97ad-2271c2f6c213(a)k4g2000yqb.googlegroups.com...
>>
>>> Where can I find this app Process Explorer?
>>
>> Type "Process Explorer" in Google then click "I'm Feeling Lucky!"
>
> Ok I found and installed Process Explorer and indeed the app is
> starting then imediately terminating.
> I wonder why this would be?
> Again using the exact same string in the Run dialog starts the app as
> expected.
> I thought that calling shell from VB was essentialy indentical to
> launching an app via the Run dialog.
>
> ?????

I'm not aware of too many differences. No idea what the curdir is when
you use Start-Run, are you? That could be one thing, if the app is
extremely inflexible in that regard.

--
..NET: It's About Trust!
http://vfred.mvps.org


From: Steve on 18 Dec 2009 14:17
> Just for kicks, you might try vbMaximized?
Tried that...no difference

> (Any chance it's just starting off-screen with vbNormal?)
I don't think so see my previous post where I mention that I actually
do see the process start in Process Explorer (thank Nobody) but then
the process is instantly killed. What I can not understand is that
the exact same command string works fine in the Run dialog.

Steve
First  |  Prev  |  Next  |  Last
Pages: 1 2 3 4 5
Prev: Unix timestamp to VB Date
Next: WebBrowser Control KeyPreview