Results 1 to 3 of 3

Thread: Upgrading a VB6-Access Application from DAO to ADO

  1. #1

    Thread Starter
    New Member
    Join Date
    Aug 2009
    Posts
    12

    Question Upgrading a VB6-Access Application from DAO to ADO

    I have an old VB6 application using a couple of .MDB database files.

    The databases were created with Access 2007, and I believe it should be a simple matter to upgrade them from .MDB to .ACCDB file format.

    I would then like to use ADO instead of DAO in the VB6 program.

    Will I encounter any unpleasant surprises?

    Is there any DAO functionality that is missing from ADO?

    Will ADO enable me to overcome the DAO limitation of 14-character database passwords?

  2. #2
    Frenzied Member
    Join Date
    Jun 2014
    Posts
    1,084

    Re: Upgrading a VB6-Access Application from DAO to ADO

    first: excuse for the late reply, just now came across this by accident

    if for access 2007 you want to go to ADO it will be a substantial rewrite of the code
    if staying with DAO (ACEDAO) the only thing you will have to change is the reference from DAO to ACEDAO

    i dont think the 14 character is a DAO limitation, it is an ACCESS limitation
    (i hear the limitation in 2007/2010 is 20 characters)

  3. #3

    Thread Starter
    New Member
    Join Date
    Aug 2009
    Posts
    12

    Re: Upgrading a VB6-Access Application from DAO to ADO

    I found by experimentation that I could use the
    Microsoft Office 12.0 Access database engine Object Library
    in place of what I was using before, Microsoft DAO 3.6 Object Library.

    This allows me to work with .ACCDB files, to use passwords of up to 20 characters, and
    to use all my existing code without modification.

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