Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. Database & SysAdmin
  3. Database
  4. OleDB and Parameters

OleDB and Parameters

Scheduled Pinned Locked Moved Database
debugginghelpquestion
3 Posts 3 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • T Offline
    T Offline
    TheMandolinMan
    wrote on last edited by
    #1

    Does anyone else get as frustrated as me trying to use Parameters with queries? How much time do you spend trying to fix "Datatype mismatch in criteria expression" or other such errors? I find these errors nearly impossible to debug and fix. There's no way I can find out which parameter is not correct. Using Parameters is supposed to make creating complex queries neat and easy, but using Parameters has been nothing but a frustration for me.

    A M 2 Replies Last reply
    0
    • T TheMandolinMan

      Does anyone else get as frustrated as me trying to use Parameters with queries? How much time do you spend trying to fix "Datatype mismatch in criteria expression" or other such errors? I find these errors nearly impossible to debug and fix. There's no way I can find out which parameter is not correct. Using Parameters is supposed to make creating complex queries neat and easy, but using Parameters has been nothing but a frustration for me.

      A Offline
      A Offline
      Ashfield
      wrote on last edited by
      #2

      TheMandolinMan wrote:

      How much time do you spend trying to fix "Datatype mismatch in criteria expression

      None. I used stored procs and look what the data type is. :) Really its just a case of getting to know your system. As a long time contractor, when I go to a new site I tend to keep an Excel doc of the main columns and their types for a quick reference - unless the site has a good current data disctionar - and believe me, not many do :)

      Bob Ashfield Consultants Ltd

      1 Reply Last reply
      0
      • T TheMandolinMan

        Does anyone else get as frustrated as me trying to use Parameters with queries? How much time do you spend trying to fix "Datatype mismatch in criteria expression" or other such errors? I find these errors nearly impossible to debug and fix. There's no way I can find out which parameter is not correct. Using Parameters is supposed to make creating complex queries neat and easy, but using Parameters has been nothing but a frustration for me.

        M Offline
        M Offline
        Mycroft Holmes
        wrote on last edited by
        #3

        I agree with Bob, I spend 0 time working out data type, a trode procedure tells you right there at the top of the proc. I then have a code generator (internally built) that writes the stub for use in the business layer. Use stored procs....

        Never underestimate the power of human stupidity RAH

        1 Reply Last reply
        0
        Reply
        • Reply as topic
        Log in to reply
        • Oldest to Newest
        • Newest to Oldest
        • Most Votes


        • Login

        • Don't have an account? Register

        • Login or register to search.
        • First post
          Last post
        0
        • Categories
        • Recent
        • Tags
        • Popular
        • World
        • Users
        • Groups