Welcome to dbFreaks.com!
FAQFAQ   SearchSearch      ProfileProfile    Private MessagesPrivate Messages   Log inLog in

Query TOO COMPLEX

 
   Database Help (Home) -> Visual Basic -> ADO RSS
Related Topics:
ADODC Query Problem - I have a VB6 form with several text boxes I would like to use to display data stored in an Access db. I've used ADODC to bind the form fields to the fields. If I use the ADODC in mode, I get all the records and it..

runtime error 3021 and user permissions - I have a VB6 that uses ADO 2.7 to access an database. I have found on Windows XP and 2000, that if the user is not part of the group, they receive: error 3021. Either BOF or EOF is true, or the current record..

updatable ado-recordset - Hi, In the code below i have an updatable However it is not working how i thought it would be. Maybe someone can help me out here? The global (Thanks to Brendan): Option Compare Database Option Explicit Public mconn As..

ADO Connection Access Database VB - I have been accessing a database on a local drive thru an ADO The following is the code that I have been using. Security The problem is now I have..

DataReport PageBreak - Hi everyone, I would like to know how to force pagebreak in a for example after 5 records printed. Thank you all
Next:  Expression Builder Missing Expressions  
Author Message
darrellwesley

External


Since: Jan 24, 2005
Posts: 2



(Msg. 1) Posted: Fri Feb 11, 2005 10:35 am
Post subject: Query TOO COMPLEX
Archived from groups: microsoft>public>vb>database>ado (more info?)

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.

 >> Stay informed about: Query TOO COMPLEX 
Back to top
Login to vote
mike w.2

External


Since: Aug 25, 2004
Posts: 1



(Msg. 2) Posted: Mon Feb 14, 2005 3:37 pm
Post subject: RE: Query TOO COMPLEX [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

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 
Back to top
Login to vote
darrellwesley

External


Since: Jan 24, 2005
Posts: 2



(Msg. 3) Posted: Tue Feb 15, 2005 6:43 am
Post subject: RE: Query TOO COMPLEX [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

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 
Back to top
Login to vote
Display posts from previous:   
   Database Help (Home) -> Visual Basic -> ADO All times are: Pacific Time (US & Canada) (change)
Page 1 of 1

 
You can post new topics in this forum
You can reply to topics in this forum
You can edit your posts in this forum
You can delete your posts in this forum
You can vote in polls in this forum



[ Contact us | Terms of Service/Privacy Policy ]