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
CODE PROJECT For Those Who Code
  • Home
  • Articles
  • FAQ
Community
  1. Home
  2. General Programming
  3. Visual Basic
  4. query engine error

query engine error

Scheduled Pinned Locked Moved Visual Basic
helpcsharpdatabasequestion
3 Posts 2 Posters 1 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.
  • I Offline
    I Offline
    illusionFinder
    wrote on last edited by
    #1

    hi there when I try to run my Vb.Net application into the client site I get an error whenever I run any report and the error is query engine error, please help me...I have nothing wrong the datatables nor datasets then why does the problem appear thanks

    D 1 Reply Last reply
    0
    • I illusionFinder

      hi there when I try to run my Vb.Net application into the client site I get an error whenever I run any report and the error is query engine error, please help me...I have nothing wrong the datatables nor datasets then why does the problem appear thanks

      D Offline
      D Offline
      Dave Kreskowiak
      wrote on last edited by
      #2

      It would appear that your database isn't where the report expects it to be. Are you using an Access database? Did you hard-code a path to this database that exists on your development machine, but doesn't exist on your clients? RageInTheMachine9532 "...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome

      I 1 Reply Last reply
      0
      • D Dave Kreskowiak

        It would appear that your database isn't where the report expects it to be. Are you using an Access database? Did you hard-code a path to this database that exists on your development machine, but doesn't exist on your clients? RageInTheMachine9532 "...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome

        I Offline
        I Offline
        illusionFinder
        wrote on last edited by
        #3

        hi i am using sql database and the path is correct :(

        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