Thanks for the response. However, the SQL Service runs under the system
account and the file has the same permissions has in test. The System
"user" on the file security is set to Full Control. Also, it does execute
through some of the code in the VB app... until it encounters the DSO
object.

Any more thoughts?

using W2K sp2, SQL2K ENT sp2





"Edgardo Valdez" <edgardovaldez@hotmail.com> wrote in message
news:065a01c34fdd$c581a300$a101280a@phx.gbl...
> I suspect permissions. Check permissions for the SQL user
> to execute or see the file on the specific folder.
>
>
> Edgardo Valdez
> MCSD, MCDBA, MCSE, MCSE+I
> Database Administrator
> http://www.edgardovaldez.us/
>
>
> >-----Original Message-----
> >I have a VB6 application that uses DSO to process olap
> databases. It was
> >built to use command line parameters for execution.
> >
> >I use xp_cmdshell to execute it through TSQL. In the
> test environment, it
> >works great. However in production, it doesn't. And
> even more strange is
> >that the exact same command line string works fine if I
> run it in the
> >command prompt on the production server. Any assistance
> would be greatly
> >appreciated.
> >
> >SQL Code:
> >
> >declare @rc int
> >declare @t varchar(500)
> >
> >SET @t = '"C:\Program Files\Data
> Center\ETLOlapProcessor1.0.5.exe" /a
> >Complete'
> >
> >EXEC @rc = xp_cmdshell @t, NO_OUTPUT
> >
> >
> >Error Info:
> >Error Source: DSO
> >Error Desc.: Object variable or With block variable not
> set
> >
> >
> >
> >.
> >