>It was me testing with limits above OS (and never tested with the sample I gave-I should:).

Yep, you should! <g> Well, I'm glad you solved the problem! =)

~~Bonnie


>>>It worked!!!???
>><snip>
>>>(and I would start to think what could I have done for it not to work:)
>>
>>Hey Cetin ... this sounds exactly like the go-round that you and I had a few days ago with the Trusted Connection differences I was having with .NET 2.0 and 1.1 ... where it worked fine with 1.1 on my machine, but not on yours (until you added the login to SQL Server). I *still* have not figured out what I've got on my machine to make it work with 1.1 and not 2.0.
>>
>>I hope you do better than me and figure out what this ShellExecute problem is!! <g>
>>
>>~~Bonnie
>
>Yes I remembered that at first too:)
>
>Neither ShellExecute nor .Net was the problem.
>The culprit was the commandline parameters I passed. It should have a limit in length and yes it had a limit (funny actually I was testing if it did have a limit - who told me to start with one over limit:).
>It was me testing with limits above OS (and never tested with the sample I gave-I should:). The returned error code made me think it was not me and I severe yesterday I tried with parameters that were very in short in length too (as all we do:)
>Cetin