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. General Programming
  3. Visual Basic
  4. ADODC ConnectionString App.Path VB6

ADODC ConnectionString App.Path VB6

Scheduled Pinned Locked Moved Visual Basic
helpcomsecurity
4 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.
  • A Offline
    A Offline
    Amit Battan Ror
    wrote on last edited by
    #1

    i am working in VB6, a window base project use a adodc control i give Adodc1.ConnectionString = "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=" & App.Path & "\sms.mdb;Persist Security Info=False" on form load and in properties window i leave blank the connection string but its not working Error: [microsoft][odbc driver manager]Data source name not found and no default drive specified and if i give any connectionstring in the properties of adodc control then it is hardcode i have to avoid that Please help me battan20@gmail.com

    A P 2 Replies Last reply
    0
    • A Amit Battan Ror

      i am working in VB6, a window base project use a adodc control i give Adodc1.ConnectionString = "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=" & App.Path & "\sms.mdb;Persist Security Info=False" on form load and in properties window i leave blank the connection string but its not working Error: [microsoft][odbc driver manager]Data source name not found and no default drive specified and if i give any connectionstring in the properties of adodc control then it is hardcode i have to avoid that Please help me battan20@gmail.com

      A Offline
      A Offline
      Amit Battan Ror
      wrote on last edited by
      #2

      i am using MS access file in that project

      J 1 Reply Last reply
      0
      • A Amit Battan Ror

        i am using MS access file in that project

        J Offline
        J Offline
        jeipiyaku
        wrote on last edited by
        #3

        how about using adodb instead of adodc? just a suggestion i have exacly no clue about your problem :-D

        1 Reply Last reply
        0
        • A Amit Battan Ror

          i am working in VB6, a window base project use a adodc control i give Adodc1.ConnectionString = "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=" & App.Path & "\sms.mdb;Persist Security Info=False" on form load and in properties window i leave blank the connection string but its not working Error: [microsoft][odbc driver manager]Data source name not found and no default drive specified and if i give any connectionstring in the properties of adodc control then it is hardcode i have to avoid that Please help me battan20@gmail.com

          P Offline
          P Offline
          Paul Conrad
          wrote on last edited by
          #4

          Amit Battan Ror wrote:

          i am working in VB6

          Sorry to hear, since VB6 has been dead for quite some time now...

          "The clue train passed his station without stopping." - John Simmons / outlaw programmer "Real programmers just throw a bunch of 1s and 0s at the computer to see what sticks" - Pete O'Hanlon

          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