> Can you put print statements in your real trigger and setup 
> and odbc_err_handler to catch them so you can see what is 
> really running?
> 
> There is an example in t/20SqlServer.t included in the 
> DBD::ODBC test suite.

Thanks! That's a great help in debugging, which I didn't know
about. Still at the noob level in MSSQL.

  $dbh->{odbc_err_handler} = sub { print STDERR Dumper \...@_ };

And in SQL, simply:

  print @pubnr;

Michael

Reply via email to