Re: Paramstr
From: Rob Kennedy (.)
Date: 11/19/03
- Next message: Gerrit Draisma: "Obscure EInvalidOp error message"
- Previous message: Ralph Freshour: "Re: Reading From A File Question"
- In reply to: Peder Hanghøj: "Paramstr"
- Next in thread: Peder Hanghøj: "Re: Paramstr"
- Reply: Peder Hanghøj: "Re: Paramstr"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Wed, 19 Nov 2003 09:52:05 -0600
"Peder Hangh�����������������������" wrote:
> I am using Delphi 6
> I am uding shellexecute in a program to start an other program with 3
> parameters:
Might I suggest you use CreateProcess instead? ShellExecute is designed
to figure out the command line automatically by looking in the registry,
and there is the potential for confusion if what it finds in the
registry doesn't match what you tell it to use.
> Shellexecute(Handle,pchar('open'),pchar('newprogram.exe'),pchar(param1+'
> '+param2+' '+param3),Pchar(''),sw_normal)
> In Newprogram.exe i am using jeg param(1)-param(3) reading the 3 parameters.
> It works fine, but...
>
> On some - only some - windows 98 mashines it does not work.
"It does not work" is a useless description. In what way does it not
work? Does your program crash? Does ShellExecute return an error code?
Are the images loaded upside-down? On what sorts of machines does it
"work"? If you're looking at the difference between Windows 95 and
Windows NT, the length of the command line may be a factor.
-- Rob
- Next message: Gerrit Draisma: "Obscure EInvalidOp error message"
- Previous message: Ralph Freshour: "Re: Reading From A File Question"
- In reply to: Peder Hanghøj: "Paramstr"
- Next in thread: Peder Hanghøj: "Re: Paramstr"
- Reply: Peder Hanghøj: "Re: Paramstr"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
