Mark L. Breen
subs at solution-providers.ie
Wed Jul 2 04:34:23 CDT 2003
Hello Paul, I think that the multiple step message is what VB sends us when SQL sends it an error. IE, VB does not try to accurately interpet the SQL error message. What I sometimes do when I have this problem is do the work in the table view or in QA, BTW, do you use VID for you DB design and building work? I think that you may have No Nulls set for the numeric, that may explain why it does not let you save a blank Let us know Mark ----- Original Message ----- From: <paul.hartland at fsmail.net> To: <accessd at databaseadvisors.com>; <dba-vb at databaseadvisors.com> Sent: Wednesday, July 02, 2003 10:14 AM Subject: [dba-VB] Muliple-step operation error - VB6 FE SQL BE > To all, > > I have a Visual Basic 6 form which is connected to a SQL Server 7.0 database using an ADO control, all of the fields are either text or date with the exception of one, which is numeric. If I enter a numeric value in this everything is fine, but if I enter text or delete the contents and then try to save the recordset I get the following error message : > > Multiple-step operation generated errors. Check each status value. > > Anyone have any ideas on why this happens ? > > Paul > > > __________________________________________________________________________ > Join Freeserve http://www.freeserve.com/time/ > > Winner of the 2003 Internet Service Providers' Association awards for Best Unmetered ISP and Best Consumer Application. > > > _______________________________________________ > dba-VB mailing list > dba-VB at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/dba-vb > http://www.databaseadvisors.com > >