Results 1 to 9 of 9

Thread: [RESOLVED] Installing the Microsoft Jet 3.51 OLE DB Provider, MDB File Access

  1. #1

    Thread Starter
    Lively Member
    Join Date
    Oct 2015
    Posts
    93

    Resolved [RESOLVED] Installing the Microsoft Jet 3.51 OLE DB Provider, MDB File Access

    Hi, i have problem with project deployment. I do not know what is missing . Form do not connect to file.
    what files need to be installed with Microsoft.Jet.OLEDB.3.51? Code is ok, runs on one pc
    Last edited by Krzysztof#; May 10th, 2017 at 07:11 AM.

  2. #2
    PowerPoster SamOscarBrown's Avatar
    Join Date
    Aug 2012
    Location
    NC, USA
    Posts
    9,145

    Re: Installing the Microsoft Jet 3.51 OLE DB Provider, MDB File Access

    Good morning, K...

    Not sure what you are asking. You say your code runs fine on A PC. Are you trying to run your program from other computers on a network and that is where you are having problems?

    Also, VERY few people will go to an external link to look at someone's code. Best if you put your applicable code in a Thread, or even attach your entire project to one.

  3. #3
    gibra
    Guest

    Re: Installing the Microsoft Jet 3.51 OLE DB Provider, MDB File Access

    Use Microsoft.Jet.OLEDB.4.00, instead, because already installed in Windows since 2000 version.
    So, you haven't to install nothing.

  4. #4

    Thread Starter
    Lively Member
    Join Date
    Oct 2015
    Posts
    93

    Re: Installing the Microsoft Jet 3.51 OLE DB Provider, MDB File Access

    Yes, trying to run program on second computer so if i have file to install with provider thought that will be enough to read its database. Ok will remember advice about posting project files, this one was too big to attach in other way than link

  5. #5

    Thread Starter
    Lively Member
    Join Date
    Oct 2015
    Posts
    93

    Re: Installing the Microsoft Jet 3.51 OLE DB Provider, MDB File Access

    Thanks gibra, good to know no addons in future projects, this one succeded hopefuly with package and deployment wizard, it added missing files great

  6. #6
    PowerPoster Elroy's Avatar
    Join Date
    Jun 2014
    Location
    Near Nashville TN
    Posts
    9,853

    Re: [RESOLVED] Installing the Microsoft Jet 3.51 OLE DB Provider, MDB File Access

    Krzysztof#,

    I'm pretty sure that the DAO360.DLL is 100% compatible with the DAO 3.51. Personally, I use the DAO 3.60 and absolutely love it. (I also make some use of the ADO in the same project, but that's another subject.)

    The DAO 3.60 is also pre-installed on all Windows machines (at least since WinXP, possibly earlier).

    You might want to consider changing your DAO reference in your project and re-compiling with the DAO 3.60.

    Good Luck,
    Elroy
    Any software I post in these forums written by me is provided "AS IS" without warranty of any kind, expressed or implied, and permission is hereby granted, free of charge and without restriction, to any person obtaining a copy. To all, peace and happiness.

  7. #7

    Thread Starter
    Lively Member
    Join Date
    Oct 2015
    Posts
    93

    Post Re: [RESOLVED] Installing the Microsoft Jet 3.51 OLE DB Provider, MDB File Access

    Ok, thank you for answers and time, in fact finished by replacing all that needed by
    Code:
    Open FilePath1 + NazwaPliku For Output As frefile 
    strData(0) = Trim(Text1.Text)
    strData(1) = Trim(Text2.Text)
    strData(2) = Trim(Text3.Text)
    Print #frefile, Join(strData, "1234")
    Close frefile
    Code:
    Open FilePath1 & frmMain.File1.List(q) For Input As #frefile
    strData = Split(Input(LOF(frefile), frefile), "1234")
    frmMain.List1.AddItem strData(0), 0
    frmMain.List2.AddItem strData(1), 0
    frmMain.List3.AddItem strData(2), 0
    Close frefile
    Last edited by Krzysztof#; May 17th, 2017 at 12:20 AM.

  8. #8
    PowerPoster
    Join Date
    Feb 2006
    Posts
    24,482

    Re: Installing the Microsoft Jet 3.51 OLE DB Provider, MDB File Access

    Quote Originally Posted by gibra View Post
    Use Microsoft.Jet.OLEDB.4.00, instead, because already installed in Windows since 2000 version.
    So, you haven't to install nothing.
    True enough, the Jet 4.0 Provider and database engine should "sniff" your MDB when you open the Connection and adapt to your old Jet3X format files. You can also specify Jet OLEDB:Engine Type=4 in your connection strings. This "4" means "3.x" as shown by the constants:

    Code:
    JET_ENGINETYPE_UNKNOWN = 0
    JET_ENGINETYPE_JET10 = 1
    JET_ENGINETYPE_JET11 = 2
    JET_ENGINETYPE_JET2X = 3
    JET_ENGINETYPE_JET3X = 4
    JET_ENGINETYPE_JET4X = 5
    JET_ENGINETYPE_DBASE3 = 10
    JET_ENGINETYPE_DBASE4 = 11
    JET_ENGINETYPE_DBASE5 = 12
    JET_ENGINETYPE_EXCEL30 = 20
    JET_ENGINETYPE_EXCEL40 = 21
    JET_ENGINETYPE_EXCEL50 = 22
    JET_ENGINETYPE_EXCEL80 = 23
    JET_ENGINETYPE_EXCEL90 =24
    JET_ENGINETYPE_EXCHANGE4 = 30
    JET_ENGINETYPE_LOTUSWK1 = 40
    JET_ENGINETYPE_LOTUSWK3 = 41
    JET_ENGINETYPE_LOTUSWK4 = 42
    JET_ENGINETYPE_PARADOX3X = 50
    JET_ENGINETYPE_PARADOX4X = 51
    JET_ENGINETYPE_PARADOX5X = 52
    JET_ENGINETYPE_PARADOX7X = 53
    JET_ENGINETYPE_TEXT1X = 60
    JET_ENGINETYPE_HTML1X = 70
    That is most useful when you must create a new Jet3X MDB.
    Last edited by dilettante; May 16th, 2017 at 06:22 PM.

  9. #9
    Addicted Member
    Join Date
    Mar 2009
    Posts
    244

    Re: Installing the Microsoft Jet 3.51 OLE DB Provider, MDB File Access

    Well, with the latest windows update it seems OleDB 4.0 (JetEngine 3.6) has a problem if the accessdatabase has a table with a fieldname longer than 32 characters, you'll get an error 'unrecognized database format' if you try o open the table. (We found out through trial and error that the length of the fieldname was the problem).
    We haven't tested yet if the problem also occurs if you use the OLEDB.3.51 version, we do know that with DAO 3.51 and DAO 3.55 don't give a problem, but DAO 3.6 will.

    No idea when (or IF) microsoft is gonna release a fix.

    Edit: one small note, it seems only if the access database is an access 97 database, 2000 doesn't seem to have a problem (but then again, we could only create the 2000 database with DAO 3.6).
    Last edited by SuperDre; Jan 10th, 2019 at 08:33 AM.

Tags for this Thread

Posting Permissions

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



Click Here to Expand Forum to Full Width