SGkgdGhlcmUsIEkndmUgZ290IGEgcHJvYmxlbToNCg0KU2l0dWF0aW9uOg0KDQpJIG9wZW4gYSBS
ZWNvcmRzZXQgd2l0aCB0aGUgZm9sbG93aW5nIGNvZGU6DQotLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0NCnJzLkFjdGl2ZUNvbm5lY3Rpb24gPSBjbg0KcnMuQ3Vyc29yTG9jYXRpb24g
PSBhZFVzZVNlcnZlcg0KcnMuQ3Vyc29yVHlwZSA9IGFkT3BlbkR5bmFtaWMNCnJzLkxvY2tUeXBl
ID0gYWRMb2NrT3B0aW1pc3RpYw0KcnMuT3BlbiAiU0VMRUNUICogRlJPTSBQRVJTT04uREJGIFdI
RVJFIFBFUlNJRCA9ICciICYgcGVyc19uciAmICInIg0KLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tDQoNCnRoZW4gSSBtYWtlIGFuIHVwZGF0ZSBvZiAxMiBmaWVsZHM6DQotLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCnJzLkZpZWxkcygiUEVSU05BTUUiKS5WYWx1ZSA9
ICJUZXN0dXNlciINCnJzLkZpZWxkcygiLi4uLi4uLmV0Yw0KLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tDQoNCmFuZCBieSB0aGUgbGluZSAicnMuVXBkYXRlIiBjb21lcyB0aGUgZm9s
bG93aW5nIGVycm9yLWNvZGU6DQoNCkVycm9yOiBbTWljcm9zb2Z0XVtPREJDIFZpc3VhbCBGb3hQ
cm8gRHJpdmVyXVNRTDogU3RhdGVtZW50IHRvbyBsb25nDQpDb2RlOiA4MDAwNDAwNQ0KU291cmNl
OiBNaWNyb3NvZnQgT0xFIERCIFByb3ZpZGVyIGZvciBPREJDIERyaXZlcnMNCg0KV2hhdHMgdGhl
IFByb2JsZW0/DQoNCkJlc3QgUmVnYXJkcywNCkQuV2lydGgNCg0KDQotLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCkRv
bWluaWMgV2lydGgNCklULUFwcHJlbnRpY2UNCkthYmEgQUcNCkhvZndpc2Vuc3RyYXNzZSAyNA0K
Q0gtODE1MyBS/G1sYW5nDQoNClRlbC4gKzQxICgwKTEgLSA4MTggOTEgMjYNCg0KRS1NYWlsOiBk
d2lydGhAa2FiYS5jb20NCkludGVybmV0OiBodHRwOi8vd3d3LmthYmEuY2gvDQpQcml2YXQ6IGh0
dHA6Ly93d3cuc3ViemVyby5jaC52dQ==

Hi there, I've got a problem:

Situation:

I open a Recordset with the following code:
---------------------------------------------------------------------------
---------------
rs.ActiveConnection = cn
rs.CursorLocation = adUseServer
rs.CursorType = adOpenDynamic
rs.LockType = adLockOptimistic
rs.Open "SELECT * FROM PERSON.DBF WHERE PERSID = '" & pers_nr & "'"
---------------------------------------------------------------------------
---------------

then I make an update of 12 fields:
---------------------------------------------------------------------------
---------------
rs.Fields("PERSNAME").Value = "Testuser"
rs.Fields(".......etc
---------------------------------------------------------------------------
---------------

and by the line "rs.Update" comes the following error-code:

Error: [Microsoft][ODBC Visual FoxPro Driver]SQL: Statement too long
Code: 80004005
Source: Microsoft OLE DB Provider for ODBC Drivers

Whats the Problem?

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C1D0E8.8AA517F0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Open the fields as rs.edit then do rs!fieldname =3D newstring then do
rs.update..

Andy..

-----Original Message-----
From: Dominic Wirth [mailto:dwirth@k...]
Sent: Thursday, March 21, 2002 9:51 AM
To: ActiveX_Data_Objects
Subject: [activex_data_objects] Error with rs.Update


Hi there, I've got a problem:

Situation:

I open a Recordset with the following code:
------------------------------------------------------------------------
----
--------------
rs.ActiveConnection =3D cn
rs.CursorLocation =3D adUseServer
rs.CursorType =3D adOpenDynamic
rs.LockType =3D adLockOptimistic
rs.Open "SELECT * FROM PERSON.DBF WHERE PERSID =3D '" & pers_nr & "'"
------------------------------------------------------------------------
----
--------------

then I make an update of 12 fields:
------------------------------------------------------------------------
----
--------------
rs.Fields("PERSNAME").Value =3D "Testuser"
rs.Fields(".......etc
------------------------------------------------------------------------
----
--------------

and by the line "rs.Update" comes the following error-code:

Error: [Microsoft][ODBC Visual FoxPro Driver]SQL: Statement too long
Code: 80004005
Source: Microsoft OLE DB Provider for ODBC Drivers

Whats the Problem?

Best Regards,
D.Wirth


---------------------------------------------------------------------
Dominic Wirth
IT-Apprentice
Kaba AG
Hofwisenstrasse 24
CH-8153 R=FCmlang

Tel. +41 (0)1 - 818 91 26

E-Mail: dwirth@k...
Internet: http://www.kaba.ch/
Privat: http://www.subzero.ch.vu
=16=A7=81=EC=A8=BA=B9sSZ)=B6*'=B1=ABa=B6=DA=7F=FE=9D=A9=C2=BA1r?=BF(tm)=A9
=DA=81=EA=DA=B2s+=B6<=A7=B2=E6=ECr=B8>z=C7=A7u=A6=E5jy=1E(tm)=A8=A5=B6?^
j=F7sr=D8=AF{=17
Z=B5=AA=1B=8D=E7-=B3=AEz=E3oV=A7jp=AEOE\