On Wed, 2004-07-21 at 23:06, amonotod wrote: > Hello, > I'm using DBD::Syabse in a script (which is working just > beautifully, thanks to the authors of DBI and the DBDs - Thank you, > people), and I'm doing some sp_add/droplogin/sp_dropdevice statements. > These also work just fine, but print message regardless of whether I > execute() them or do() them... > > Device dropped. > Device dropped. > Account locked. > Login dropped. > Password correctly set. > Account unlocked. > New login created.
These "messages" are generated via "PRINT" statements in the stored procedures. PRINT statements are sent to the client via the server message callback, with an error number of 0. You can trap these by using an error handler. See the syb_err_handler attribute in the DBD::Sybase docs for details. Michael -- Michael Peppler Data Migrations, Inc. [EMAIL PROTECTED] http://www.peppler.org/ Sybase T-SQL/OpenClient/OpenServer/C/Perl developer available for short or long term contract positions - http://www.peppler.org/resume.html
