Results 1 to 6 of 6

Thread: Unrecognised Database format

  1. #1

    Thread Starter
    Member
    Join Date
    Oct 2000
    Location
    chennai,india
    Posts
    44

    Lightbulb

    Hi
    i have got another problem. i am have designed the database using VisDAta from VB6.0(.mdb file). Everything works fine when i don't have ACCESS 2000. My problem arises when i open it in Access 2000. It says Unrecognised data format. I tried compacting /repairing it, but it displays the same error "Unregonised data format"

    How to solve this problem?

    thanx in advance
    sundar

  2. #2
    Guest
    Hi Sundar, it should be relieving for u to know that u r not the first person to fall for this. Yes this problem is still existing as it is problem with the Jet i suppose. Microsoft claims to have solved this in SP4 of VB6. Why actually the problem ? even i dont know. But how to get rid of it ? my answer would be to use upgrade to SP4. Access 2000 throws this error for all the previous versions of access databases. By the way, do you know that Access 2000 doesnt support DAO objects until SP4.
    Please check it out and i suggest you use ADO if u still in the starting stages.

    all the best...vijay

  3. #3
    Randalf the Red honeybee's Avatar
    Join Date
    Jun 2000
    Location
    off others' brains
    Posts
    4,345

    Well ...

    sundarv, yes, you are not the first one to be bitten by the VB6-Access 2000-Access 97 problem.

    The thing is MS claims that VB6 works best with Access2K, but not without a series of service packs, with their own problems. And then the in-built features of VB, like the VisData and many of the Wizards and Addins fail to work with Access 2000.

    At the same time, I would like to correct GantiBabu also. VB6-Access2K works with SP3, not SP4. SP3 has the necessary DAO file, version 3.6 which allows you to use an Access 2000 database. The DAO version used with Access 97 was 3.51.

    Also in case of ADO, while connecting to Access 2000, you need to select the Jet OLEDB Provider 4.

    sundarv, your problem is you have used VisData to create the database, which was created in Access 97 format. If you open it in Access 2000, you will face some problems. But I have opened Access 97 mdb files in Access 2000, and only got a message saying I had to convert the database to Access 2K format or else it would be read only. It didn't directly say 'Unrecognized format' or something.

    I am not a complete idiot. Some parts are still missing.
    Check out the rtf-help tutorial
    General VB Faq Thread
    Change is the only constant thing. I have not changed my signature in a long while and now it has started to stink!
    Get more power for your floppy disks. ; View honeybee's Elite Club:
    Use meaningfull thread titles. And add "[Resolved]" in the thread title when you have got a satisfactory response.
    And if that response was mine, please think about giving me a rep. I like to collect them!

  4. #4
    New Member
    Join Date
    May 2000
    Location
    Philippines
    Posts
    6

    Unhappy

    i myself have problem with this, i installed service pack 4 now i dont get the error "unrecognized database format" but instead this error "uninstallable ISAM"....
    leagle

  5. #5
    Guest
    Hi honeybee, thanx for the reference, and yes i have even tried DAO 3.6 library with Provider as OLEDB 4 but still i had the problems with SP3 and so i came to that conclusion. But, now, since u say that i might as well check it out again. Thanx anyway for that piece of info.

    With regards...vijay

  6. #6
    Lively Member
    Join Date
    Aug 2000
    Location
    Australia
    Posts
    82

    My $0.02 worth

    Yes, VB6 SP3 did include DA0 3.6 for Access2k, however, if you wanted to use the Data Control, you had to install SP4 as the Data Control in SP3 would not connect to an Access2k DB.

    Re the problem of "uninstallable ISAM". Are you running Windows 2000? A colleague of mine who installed one of my programmes onto his Win2k laptop got the same error message. Turned out that he had to have ultimate Administrator rights on his machine for all of the various Jet DLL's to be properly registered.

    Just a thought.

    Cheers
    Adrian.

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