the FIND method vs SQL WHERE

Results 1 to 3 of 3

Thread: the FIND method vs SQL WHERE

  1. #1
    rossman Guest

    Default the FIND method vs SQL WHERE

    Does anyone know why this doesn&#039t work? I thought that the find method took the place of SQL WHERE. Isn&#039t it the same syntax? Is there some other way I should be doing this?<BR><BR>GiftInfo.Find("OrderID like &#039" & strID & "*&#039 and RctSent = null")<BR><BR>Here&#039s the error:<BR>Arguments are of the wrong type, are out of acceptable range, or are in conflict with one another. <BR><BR>RctSent is bin and<BR>OrderID is Char<BR><BR>what am I doing wrong?<BR>

  2. #2
    Join Date
    Dec 1969

    Default RE: the FIND method vs SQL WHERE

    FIND gives a much higher overhead than SQL WHERE - and DEFINITELY doesn&#039t replace it....<BR><BR>as far as i know, find doesn&#039t actually take a SQL statement as argument, but don&#039t quote me on that.<BR><BR>if i were you i&#039d go back to using WHERE, it&#039s easier, with lower resource overhead and it&#039s designed for this.<BR><BR>jason<BR><BR>

  3. #3
    BMonday Guest

    Default RE: the FIND method vs SQL WHERE

    Nope, you can&#039t do that. Find will only work on one criteria, that is documented as a limitation on MS&#039 web site.<BR><BR>Also I have never seen Find used to execute a SQL query.<BR><BR>Beau

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts