The rkva field is defined as a "decimal" data type with a precision of 6 and
scale of 1. The "tapdesc" field as a length of 40 and the "secdesc" a length
of 20.
Obviously the text fields are not the problem, is the decimal field causing
the problem?
"mike w." wrote:
> usually means data types aren't matching or a text filed is too small for
> what you are inserting
>
>
> mike w.
>
> "Darrell Wesley" wrote:
>
> > Here is a code snipet that produces a "too complex" error message
> >
> > Set DsgnData = New ADODB.Recordset
> > sql = "Select * from dsgndata where coilspec = '" & CoilSpec & "'"
> > With DsgnData
> > .Source = sql
> > .CursorLocation = adUseClient
> > .CursorType = adOpenDynamic
> > .LockType = adLockOptimistic
> > .ActiveConnection = OrdMntCnn
> > .Open
> > End With
> >
> > DsgnData("rkva") = kva3 ====> 750
> > DsgnData("tapdesc") = atap ====> "NO TAP"
> > DsgnData("secdesc") = asec =====> "SOMETHING ELSE"
> > DsgnData.Update ====> Query too complex
> >
> > Why is this "TOO COMPEX" and how can I get around it with out implementing a
> > SQL UPDATE query.
> >
> >
> ><!-- ~MESSAGE_AFTER~ -->
>> Stay informed about: Query TOO COMPLEX