Re: Multiple-step Operations Generated Errors
From: Emile Petrus (emile_at_think.com.br)
Date: 04/17/04
- Next message: kissdadog: "!!!! A chance of a lifetime !!!"
- Previous message: Del Murray: "Re: ADO Recordsets"
- In reply to: Brian Bushay TeamB: "Re: Multiple-step Operations Generated Errors"
- Next in thread: Brian Bushay TeamB: "Re: Multiple-step Operations Generated Errors"
- Reply: Brian Bushay TeamB: "Re: Multiple-step Operations Generated Errors"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: 16 Apr 2004 20:04:40 -0700
Brian Bushay TeamB <BBushay@Nmpls.com> wrote:
>
>>SQL Server 2000 - TADODataSet
>>
>>Create table client (id int identity (1,1),
>> name varchar(100),
>> date datetime default (getdate()))
>>
>>When I try to insert a new record the SQL Server must return two values: new id and the date.
>>
>>It is work fine if CursorLocation property is clUseServer.
>>
>>If I use CursorLocation = clUseClient then it is raised the message 'Multiple-step Operations Generated Errors'
>
>Date is an SQL key word my guess is using Date as a field name is the source of
>your problem.
>--
>Brian Bushay (TeamB)
>Bbushay@NMPLS.com
This is an example. The real name of the field is not 'date'. The problem is the default property. If there are more then one the error is raised.
Thanks anyway
- Next message: kissdadog: "!!!! A chance of a lifetime !!!"
- Previous message: Del Murray: "Re: ADO Recordsets"
- In reply to: Brian Bushay TeamB: "Re: Multiple-step Operations Generated Errors"
- Next in thread: Brian Bushay TeamB: "Re: Multiple-step Operations Generated Errors"
- Reply: Brian Bushay TeamB: "Re: Multiple-step Operations Generated Errors"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|