hi there,

i am using the 'run command line' function to run osql.exe which executes a sql script on a sql server. i then look at %_SB_ERRORCODE% to confirm it ran ok.

it seems to me that %_SB_ERRORCODE% only produces a 1 or 0 for an osql execution. this makes installation troubleshooting a bit difficult because an error could occur in numerous places and it would be useful to let the user know exactly what type of error occurred. eg it could be a problem with a foreign key violation in the database, or it could be that the user does not have permissions on the sql server.

i found some previous forum posts that advise that native sql execution is on the cards for SetupBuilder some time in the future. has this been progressed? if not, is there a way of getting the precise error details for an osql execution?

thanks

rob