Multiple-step OLE DB operation generated errors.

------=_Part_2382_8121946.1121216089760
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

I've a situation here..!=20
An error occurs when I try to update a record to mytable.=20

Multiple-step OLE DB operation generated errors. Check each OLE DB status=
=20
value, if available. No work was done.=20

Err : -2147217887=20

Finidings:-=20

This happence to the field which is created as TEXT or VarChar type..!!=20
While skipping those fields in Debug Mode, Data Storing to the Database=20

OS: XP=20
Connectivity : ODBC=20
Application : VB6/ADO Object Method=20

If any one have experianced about this please Suggest me how to solve the=
=20
issue.=20


Create Table tblJournal=20
(=20
fldAccountID Int(4) NOT NULL,=20
fldID Int(6) NOT NULL,=20
fldSerial Int(4) NOT NULL,=20
fldModuleID Int(6) NOT NULL,=20
-----=20
-----=20
-----=20
fldNarration varChar(80) NULL,=20
fldByLedgerID Int(6) NOT NULL,=20
fldTagID Int(6) DEFAULT 0,=20
fldProjectID Int(6) DEFAULT 0,=20
fldModeOfPayment Int(1) DEFAULT 1,=20
fldNameOfBank varChar(100) Null,=20
fldPlace varChar(100) Null,=20
fldRefNo varChar(50) Null,=20
fldDated Date ,=20
fldDeleted Int(1)DEFAULT 0=20


);=20

The error occurs either in fldNarration, fldNameOfBank, fldPlace, fldRefNo=
=20
fldNarration was actually TEXT type..=20

So please

------=_Part_2382_8121946.1121216089760--

RE: Multiple-step OLE DB operation generated errors.

Check you version of MDAC
(http://www.microsoft.com/downloads/details.aspx?FamilyID=8f 0a8df6-4a21-4b43
-bf53-14332ef092c9&displaylang=en)
Or search MS for cc_pkg.exe. This tool will tell you what version you are
running.

I had the same probem with a machine running MDAC v2.6. When I upgraded to
v2.8 the problem dissappeared. I can't guarantee that it will fix the
problem, but it did work in my case.

Justin


-----Original Message-----
From: Aiby [mailto:aibydas@gmail.com]
Sent: Tuesday, July 12, 2005 8:55 PM
To: myodbc@lists.mysql.com
Subject: Multiple-step OLE DB operation generated errors.

I've a situation here..!
An error occurs when I try to update a record to mytable.

Multiple-step OLE DB operation generated errors. Check each OLE DB status
value, if available. No work was done.

Err : -2147217887

Finidings:-

This happence to the field which is created as TEXT or VarChar type..!!
While skipping those fields in Debug Mode, Data Storing to the Database

OS: XP
Connectivity : ODBC
Application : VB6/ADO Object Method

If any one have experianced about this please Suggest me how to solve the
issue.


Create Table tblJournal
(
fldAccountID Int(4) NOT NULL,
fldID Int(6) NOT NULL,
fldSerial Int(4) NOT NULL,
fldModuleID Int(6) NOT NULL,
-----
-----
-----
fldNarration varChar(80) NULL,
fldByLedgerID Int(6) NOT NULL,
fldTagID Int(6) DEFAULT 0,
fldProjectID Int(6) DEFAULT 0,
fldModeOfPayment Int(1) DEFAULT 1,
fldNameOfBank varChar(100) Null,
fldPlace varChar(100) Null,
fldRefNo varChar(50) Null,
fldDated Date ,
fldDeleted Int(1)DEFAULT 0


);

The error occurs either in fldNarration, fldNameOfBank, fldPlace, fldRefNo
fldNarration was actually TEXT type..

So please


--
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe: http://lists.mysql.com/myodbc?unsub=gcdmo-myodbc@m.gmane.org

Re: Multiple-step OLE DB operation generated errors.

------=_Part_4333_32554372.1121266927724
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Hello Luis
Yes! I was wondering How that Connection String Works!!! You didnt=20
specified the Provider or any thing like!!
Which application tool you use to program..! Ok let me explain few of my=20
obervations..! This code was working previously when i was trying this with=
=20
WIN98/VisualStudio6 Enviornments.
Now I am switched them to XP Professiona/ VB6 + Don.net
Environments.. So the same code is not working..!!
Many people suggested
MDAC 2.8 will solve the issue.. I found many discussion on net!!=20
Unfortunalty its not working..!=20
Now see...!
When you try to open an ActiveX Data Objects (ADO) connection ( or say=20
Operations with RecordSet Object), you may receive the following error=20
message:=20
Run-time error '-2147217887 (80040e21):'

Multiple-step OLE DB operation generated errors. Check each OLE DB status=
=20
value, if available. No work was done=20

The following are two possible causes of this error:=20
=20
In the registry, under the key for an OLE DB provider's CLSID, there may be=
=20
an entry named OLEDB_SERVICES. If the OLE DB provider that is used to make=
=20
the ADO connection does not have the OLEDB_SERVICES entry, and ADO tries to=
=20
set up a property that is not supported by the provider, the error occurs.=
=20

If OLEDB_SERVICES entry exists but there is a problem in the ADO=20
connection string, the error occurs.
If the OLEDB_SERVICES registry entry is not present, the call to set up a=
=20
property is made directly to the provider. If the provider does not support=
=20
the property, the *SetProperties* OLE DB call made by ADO will fail. This i=
s=20
a fatal failure if the property is required to make a connection. If the=20
property was explicitly included in the connection string, it is probably=
=20
required.=20

If the property setting is optional, the failure is not fatal. This is the=
=20
case when you connect without explicitly setting the property in the=20
connection string. In this case, ADO sets the property to True but marks it=
=20
as optional.=20
So these could be the posible Reasons for the sitation...=20
How it can be solved, thats my worry...! I am loosing my time..!=20
Rahul


On 7/13/05, Lu=EDs Damas wrote:=20
>=20
> any question????
>=20
> Citando Aiby :
>=20
> > !
> >
> > On 7/13/05, Lu=EDs Damas wrote:
> > >
> > > Hi there.
> > > My connection string is:
> > >
> > >=20
> CONN=3D"DSN=3DEMPXXX;DATABASE=3DEMPXXX;USER=3Droot;PWD=3Dpas sword;SERVER=
=3Dlocalhost;PORT=3D;STMT=3D;"
> > > In the ODBC connector I have the following selected:
> > > + Return Matching Rows.
> > > + Allow Big Results
> > > + Change BIGINT Columns to Int
> > > Regards
> > >
> > > ----- Original Message -----
> > > *From:* Aiby
> > > *To:* Lu=EDs Damas
> > > *Sent:* Wednesday, July 13, 2005 4:38 AM
> > > *Subject:* Re: Multiple-step OLE DB operation generated errors.
> > >
> > > Connection string is
> > > mvarConnection.ConnectionString =3D "Provider=3DMSDASQL.1;Persist Sec=
urity
> > > Info=3DFalse;Data Source=3DdsnERP"
> > > dsnERP is a dsn connection
> > > While debuging I found this happence only in certain field type.. But
> > > many people experianced this error Message in different way..
> > > Let me know How do you used the connection string in your ADO ( Just=
=20
> for
> > > a comparison )
> > >
> > >
> > > On 7/13/05, Lu=EDs Damas wrote:
> > > >
> > > > Hi.
> > > > I'm using the same tool and operating system version. My Mysql is a
> > > > little bit older, mas all works fine.
> > > > What is your connection string and ODBC parameters selected?
> > > > Regards
> > > > Luis Damas
> > > >
> > > > ----- Original Message -----
> > > > *From:* Aiby
> > > > *To:* Lu=EDs Damas
> > > > *Sent:* Wednesday, July 13, 2005 2:50 AM
> > > > *Subject:* Re: Multiple-step OLE DB operation generated errors.
> > > >
> > > > I am using XP Professiona SP2
> > > > *MDAC 2.8 SP1 ON WINDOWS XP SP2*
> > > > MySQL 4.1.12
> > > > MyODBC-3.51.11-2-win
> > > > Development Tool VB6 ( Ref: Microsoft ADO 2.8 Library )
> > > > Still gets this Error
> > > >
> > > > On 7/13/05, Lu=EDs Damas wrote:
> > > > >
> > > > > Hi there.
> > > > > I solve that kind of issue installing the last version of MDAC
> > > > > ( www.microsoft.com/data <
> http://www.microsoft.com/data>). (2.8)
> > > > > Check if it works for you.
> > > > >
> > > > > Regards
> > > > > Luis Damas
> > > > > ----- Original Message -----
> > > > > From: "Aiby" < aibydas@gmail.com>
> > > > > To: < myodbc@lists.mysql.com>
> > > > > Sent: Wednesday, July 13, 2005 1:54 AM
> > > > > Subject: Multiple-step OLE DB operation generated errors.
> > > > >
> > > > >
> > > > > I've a situation here..!
> > > > > An error occurs when I try to update a record to mytable.
> > > > >
> > > > > Multiple-step OLE DB operation generated errors. Check each OLE D=
B
> > > > > status
> > > > > value, if available. No work was done.
> > > > >
> > > > > Err : -2147217887
> > > > >
> > > > > Finidings:-
> > > > >
> > > > > This happence to the field which is created as TEXT or VarChar
> > > > > type..!!
> > > > > While skipping those fields in Debug Mode, Data Storing to the
> > > > > Database
> > > > >
> > > > > OS: XP
> > > > > Connectivity : ODBC
> > > > > Application : VB6/ADO Object Method
> > > > >
> > > > > If any one have experianced about this please Suggest me how to=
=20
> solve
> > > > > the
> > > > > issue.
> > > > >
> > > > >
> > > > > Create Table tblJournal
> > > > > (
> > > > > fldAccountID Int(4) NOT NULL,
> > > > > fldID Int(6) NOT NULL,
> > > > > fldSerial Int(4) NOT NULL,
> > > > > fldModuleID Int(6) NOT NULL,
> > > > > -----
> > > > > -----
> > > > > -----
> > > > > fldNarration varChar(80) NULL,
> > > > > fldByLedgerID Int(6) NOT NULL,
> > > > > fldTagID Int(6) DEFAULT 0,
> > > > > fldProjectID Int(6) DEFAULT 0,
> > > > > fldModeOfPayment Int(1) DEFAULT 1,
> > > > > fldNameOfBank varChar(100) Null,
> > > > > fldPlace varChar(100) Null,
> > > > > fldRefNo varChar(50) Null,
> > > > > fldDated Date ,
> > > > > fldDeleted Int(1)DEFAULT 0
> > > > >
> > > > >
> > > > > );
> > > > >
> > > > > The error occurs either in fldNarration, fldNameOfBank, fldPlace,
> > > > > fldRefNo
> > > > > fldNarration was actually TEXT type..
> > > > >
> > > > > So please
> > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > Aiby
> > > >
> > > >
> > >
> > >
> > > --
> > > Aiby
> > >
> > >
> >
> >
> > --
> > Aiby
> >
>=20
>=20
> Lu=EDs Damas
> samad@mail.telepac.pt
>=20
>=20


--=20
Aiby

------=_Part_4333_32554372.1121266927724--

Re: Multiple-step OLE DB operation generated errors.

>If the property setting is optional, the failure is not fatal. This is the
>case when you connect without explicitly setting the property in the
>connection string. In this case, ADO sets the property to True but marks it
>as optional.
> So these could be the posible Reasons for the sitation...
> How it can be solved, thats my worry...! I am loosing my time..!
> Rahul
>
>
Please file this as a bug. Please include any supporting examples.

--
Peter Harvey, Software Developer
MySQL AB, www.mysql.com

Are you MySQL certified? www.mysql.com/certification



--
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe: http://lists.mysql.com/myodbc?unsub=gcdmo-myodbc@m.gmane.org

Re: Multiple-step OLE DB operation generated errors.

------=_Part_5425_31719275.1121279876147
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

I have reported an error cause while MySQL ODCB with ADO=20
Many people shared their experiance with me... Sugested may online posting.=
..=20
Finaly I came to a concultion its not my heard ware or required software=20
problem.. But its a Bug..
But some othe way .. accepting some Limitations we can solve this..=20
proble.!!
This error is generated from ado.Recordset Objects intraction with MySQL=20
ODBC..=20
Simply avoid Recordset Object!!=20
The error caused when I tried to insert or assing values to a TEXT/VarChar=
=20
type data fields.=20
eg:- : *Rec.AddNew*
* Rec!fldMemo =3D mstrMemoText*
* -----*
* -----
*
* -----
Rec.Update

*Known cause of problem i already send to you people..
=20
When you try to open an ActiveX Data Objects (ADO) connection ( or say=20
> Operations with RecordSet Object), you may receive the following error=20
> message:=20
> Run-time error '-2147217887 (80040e21):'
>=20
> Multiple-step OLE DB operation generated errors. Check each OLE DB status=
=20
> value, if available. No work was done=20
>=20
> The following are two possible causes of this error:=20
> =20
> In the registry, under the key for an OLE DB provider's CLSID, there may=
=20
> be an entry named OLEDB_SERVICES. If the OLE DB provider that is used to=
=20
> make the ADO connection does not have the OLEDB_SERVICES entry, and ADO=
=20
> tries to set up a property that is not supported by the provider, the err=
or=20
> occurs.=20
>=20
> If OLEDB_SERVICES entry exists but there is a problem in the ADO=20
> connection string, the error occurs.
> If the OLEDB_SERVICES registry entry is not present, the call to set up a=
=20
> property is made directly to the provider. If the provider does not suppo=
rt=20
> the property, the *SetProperties* OLE DB call made by ADO will fail. This=
=20
> is a fatal failure if the property is required to make a connection. If t=
he=20
> property was explicitly included in the connection string, it is probably=
=20
> required.=20
>=20
> If the property setting is optional, the failure is not fatal. This is th=
e=20
> case when you connect without explicitly setting the property in the=20
> connection string. In this case, ADO sets the property to True but marks =
it=20
> as optional.=20
> =20
*Resolution*
Accepting certain limitation we can do the same thing in VB/ADO. Avoid=20
RecordSet object and use *INSERT query* with *ADO.Connection *objects*Execu=
te
* method.
eg:- *mSQL =3D "INSERT INTO tblName () VALUES ()"*
* adoConnection.Execute mSQL*
Here this will temperorly solve the issue..=20
But Generating INSER Query sting .. in complecated third tire business rule=
=20
will make you exhasted..
Limits field wise debuging.
Reduce readability ( depends the problem wise )
Not easy to modify. these are the few from the list
I am not sure wether this will create and issues in Transaction (Rollback=
)
How to do a RecordLocking in such circumstance.. etc
So folks.. Hopes you people fill give me a final feed back to me...
Thanking you all=20
Its=20
Rahul..
On 7/13/05, Aiby wrote:

>=20
>=20
> I've a situation here..!=20
> An error occurs when I try to update a record to mytable.=20
>=20
> Multiple-step OLE DB operation generated errors. Check each OLE DB status=
=20
> value, if available. No work was done.=20
>=20
> Err : -2147217887=20
>=20
> Finidings:-=20
>=20
> This happence to the field which is created as TEXT or VarChar type..!!=
=20
> While skipping those fields in Debug Mode, Data Storing to the Database=
=20
>=20
> OS: XP=20
> Connectivity : ODBC=20
> Application : VB6/ADO Object Method=20
>=20
> If any one have experianced about this please Suggest me how to solve the=
=20
> issue.=20
>=20
>=20
> Create Table tblJournal=20
> (=20
> fldAccountID Int(4) NOT NULL,=20
> fldID Int(6) NOT NULL,=20
> fldSerial Int(4) NOT NULL,=20
> fldModuleID Int(6) NOT NULL,=20
> -----=20
> -----=20
> -----=20
> fldNarration varChar(80) NULL,=20
> fldByLedgerID Int(6) NOT NULL,=20
> fldTagID Int(6) DEFAULT 0,=20
> fldProjectID Int(6) DEFAULT 0,=20
> fldModeOfPayment Int(1) DEFAULT 1,=20
> fldNameOfBank varChar(100) Null,=20
> fldPlace varChar(100) Null,=20
> fldRefNo varChar(50) Null,=20
> fldDated Date ,=20
> fldDeleted Int(1)DEFAULT 0=20
>=20
>=20
> );=20
>=20
> The error occurs either in fldNarration, fldNameOfBank, fldPlace, fldRefN=
o=20
>=20
> fldNarration was actually TEXT type..=20
>=20
> So please
>=20



--=20
Aiby

------=_Part_5425_31719275.1121279876147--

call procedure with ODBC

Hi,

I designed a stored procedure which is a select query. I did not create it
as a view, because I need to send some values as parameters for my
selection.

If I call the procedure with the mysql client, I get the table of results as
I wanted, by it I send the call procedure command by ODBC (with Microsoft
query), I get the message " in a stored procedure, a select must have
into").

Does it mean that ODBC does not support stored procedures ?

Xavier


CONFIDENTIALITY NOTICE - The information contained in this message and any accompanying documents may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. Thank you.

NOTE DE CONFIDENTIALITE - Ce message et toutes les pieces jointes (ci-apres le "message") sont etablis a l'intention exclusive de ses destinataires et sont confidentiels. Si vous recevez ce message par erreur, merci de le detruire et d'en avertir immediatement l'expediteur. Toute utilisation de ce message non conforme a sa destination, toute diffusion ou toute publication, totale ou partielle, est interdite, sauf autorisation expresse. L'internet ne permettant pas d'assurer l'integrite de ce message, Ubiqus (et ses filiales) decline(nt) toute responsabilite au titre de ce message, dans l'hypothese ou il aurait ete modifie.


--
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe: http://lists.mysql.com/myodbc?unsub=gcdmo-myodbc@m.gmane.org

RE: call procedure with ODBC

You need the updated version of myODBC which hasn't been released yet.
There was an email saying the Alpha version should be out in a couple of
weeks.=20

-----Original Message-----
From: Xavier Pointe [mailto:xpointe@ubiqus.com]=20
Sent: Friday, July 15, 2005 10:36 AM
To: myodbc@lists.mysql.com
Subject: call procedure with ODBC


Hi,

I designed a stored procedure which is a select query. I did not create
it as a view, because I need to send some values as parameters for my
selection.

If I call the procedure with the mysql client, I get the table of
results as I wanted, by it I send the call procedure command by ODBC
(with Microsoft query), I get the message " in a stored procedure, a
select must have into").

Does it mean that ODBC does not support stored procedures ?

Xavier


CONFIDENTIALITY NOTICE - The information contained in this message and
any accompanying documents may be privileged and confidential and
protected from disclosure. If the reader of this message is not the
intended recipient, or an employee or agent responsible for delivering
this message to the intended recipient, you are hereby notified that any
dissemination, distribution or copying of this communication is strictly
prohibited. If you have received this communication in error, please
notify us immediately by replying to the message and deleting it from
your computer. Thank you.

NOTE DE CONFIDENTIALITE - Ce message et toutes les pieces jointes
(ci-apres le "message") sont etablis a l'intention exclusive de ses
destinataires et sont confidentiels. Si vous recevez ce message par
erreur, merci de le detruire et d'en avertir immediatement l'expediteur.
Toute utilisation de ce message non conforme a sa destination, toute
diffusion ou toute publication, totale ou partielle, est interdite, sauf
autorisation expresse. L'internet ne permettant pas d'assurer
l'integrite de ce message, Ubiqus (et ses filiales) decline(nt) toute
responsabilite au titre de ce message, dans l'hypothese ou il aurait ete
modifie.


--=20
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe:
http://lists.mysql.com/myodbc?unsub=3Dmhoover@gpwlaw-mi.com


--
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe: http://lists.mysql.com/myodbc?unsub=3Dgcdmo-myodbc@m.gmane.o rg

RE: Multiple-step OLE DB operation generated errors.

When I work with ADO and MySQL I use a routine like the following to
handle the interaction.

Public Function RunSQL(SQL As String) As ADODB.Recordset
Dim rs As ADODB.Recordset
Dim Cmd As String
Dim Msg As String
Dim E As ADODB.Error
=20
On Local Error GoTo RunSQL_Err
=20
Cmd =3D UCase(Left(SQL, 4))
If Cmd =3D "SELE" Or Cmd =3D "SHOW" Then
' SELECT or SHOW can return a recordset
Set rs =3D New ADODB.Recordset
rs.Open SQL, gCon, adOpenStatic, adLockReadOnly, adCmdText
Set RunSQL =3D rs
Else
' An action query, don't worry about recordset
gCon.Execute SQL, gRecordsAffected, adCmdText
End If

RunSQL_Exit:
Exit Function
=20
RunSQL_Err:
If gCon.Errors.Count <> 0 Then
Msg =3D "SQL Error " & CStr(Err.Number) & ": " & Err.Description
For Each E In gCon.Errors
Msg =3D Msg & vbCrLf & E.Description
Next E
gCon.Errors.Clear
Msg =3D Msg & vbCrLf & "SQL: " & SQL
MsgBox Msg, , "RunSQL"
Else
MsgBox "Error " & CStr(Err.Number) & ": " & Err.Description, ,
"RunSQL"
End If
Resume RunSQL_Exit
End Function

Even if you don't operate like this, you will find it helpful to include
some error reporting as shown above whenever you get errors in ADO
operations. There can often be a cascade of errors and normally you only
see the last one. If you repoart all the errors you will often find
something there that gives you the clue about what to change.

John Bonnett

-----Original Message-----
From: Aiby [mailto:aibydas@gmail.com]=20
Sent: Wednesday, 13 July 2005 10:25 AM
To: myodbc@lists.mysql.com
Subject: Multiple-step OLE DB operation generated errors.

I've a situation here..!=20
An error occurs when I try to update a record to mytable.=20

Multiple-step OLE DB operation generated errors. Check each OLE DB
status=20
value, if available. No work was done.=20

Err : -2147217887=20

Finidings:-=20

This happence to the field which is created as TEXT or VarChar type..!!=20
While skipping those fields in Debug Mode, Data Storing to the Database=20

OS: XP=20
Connectivity : ODBC=20
Application : VB6/ADO Object Method=20

If any one have experianced about this please Suggest me how to solve
the=20
issue.=20


Create Table tblJournal=20
(=20
fldAccountID Int(4) NOT NULL,=20
fldID Int(6) NOT NULL,=20
fldSerial Int(4) NOT NULL,=20
fldModuleID Int(6) NOT NULL,=20
-----=20
-----=20
-----=20
fldNarration varChar(80) NULL,=20
fldByLedgerID Int(6) NOT NULL,=20
fldTagID Int(6) DEFAULT 0,=20
fldProjectID Int(6) DEFAULT 0,=20
fldModeOfPayment Int(1) DEFAULT 1,=20
fldNameOfBank varChar(100) Null,=20
fldPlace varChar(100) Null,=20
fldRefNo varChar(50) Null,=20
fldDated Date ,=20
fldDeleted Int(1)DEFAULT 0=20


);=20

The error occurs either in fldNarration, fldNameOfBank, fldPlace,
fldRefNo=20
fldNarration was actually TEXT type..=20

So please

--
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe: http://lists.mysql.com/myodbc?unsub=3Dgcdmo-myodbc@m.gmane.o rg