Results 1 to 5 of 5
  1. #1
    4 Star Lounger
    Join Date
    Jun 2001
    Location
    Sacramento, California, USA
    Posts
    491
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Error 3011 (WIN 2000 Acc 97)

    I created a database on Win95/Access 2000. Then I converted it "To a Previous Version", put it on a floppy,
    and brought it to work.
    Here, I have Windows 2000 and Access 97.
    I received the attached message.

    How would this system table be missing? Did it happen during conversion?
    Why did this happen and what is the fix?

    Thank you,
    Michael Abrams
    Attached Files Attached Files

  2. #2
    Plutonium Lounger
    Join Date
    Mar 2002
    Posts
    84,353
    Thanks
    0
    Thanked 29 Times in 29 Posts

    Re: Error 3011 (WIN 2000 Acc 97)

    Apparently, the converted database is corrupt. I have no idea what might have caused this. You might try the following:

    (1) Create a new, empty database.
    (2) Turn of display of System Objects.
    (3) Try to import all objects from the problematic database.

    If this doesn't work, I'm afraid you'll have to go back to the Access 2000 version and convert it again.

  3. #3
    Super Moderator
    Join Date
    Aug 2001
    Location
    Evergreen, CO, USA
    Posts
    6,623
    Thanks
    3
    Thanked 60 Times in 60 Posts

    Re: Error 3011 (WIN 2000 Acc 97)

    It sounds as though you may have security active at your work location, and not have it active at home. Best bet is to import everything out of the database into a new blank database.
    Wendell

  4. #4
    4 Star Lounger
    Join Date
    Jun 2001
    Location
    Sacramento, California, USA
    Posts
    491
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Error 3011 (WIN 2000 Acc 97)

    Guess I'll have to wait til I get home. I will import it all into a fresh db and try the conversion again.

    Out of curiousity, we use the term "corruption" a lot on these Access boards.

    Is there a paper out there that lists possible sources of this corruption? I realize it is a generic
    term, but I always wonder how a database gets corrupt (like in my case) from certain situations (like conversion).

    Thanks again!! I'll try it again tomorrow and post if there is still a problem.

    Michael

  5. #5
    Super Moderator
    Join Date
    Aug 2001
    Location
    Evergreen, CO, USA
    Posts
    6,623
    Thanks
    3
    Thanked 60 Times in 60 Posts

    Re: Error 3011 (WIN 2000 Acc 97)

    I don't think there is a definitive thread that covers all of the possible sources of corruption, but -
    <UL><LI>workstation crashes or Access crashes are probably the most common cause,
    <LI>network problems which occur during the transfer of data to the mdb file can cause corruption on unstable networks,
    <LI>users turning off PCs (or power failures) will cause corruption,
    <LI>software bugs that create corruption - these are probably the least common cause of corruption (although there were some bugs in the initial realease of A2K that were issues until SR-1 of Office2K)[/list]So what can you do to minimize problems -
    <UL><LI>Split your application into a front-end that runs on the local workstation and a back-end that is on a shared resource
    <LI>Avoid the use of memo or object-types of fields if possible
    <LI>Use Access 2000 or 2002 - they are more robust than Access 97
    <LI>Don't use an Access 97 back-end with an Access 2000/2002 unless you absolutely have to, and then do it for the minimum time that you can
    <LI>Make sure you have all the latest services packs for both your workstation OS and for Access
    <LI>Train you users on what not to do
    <LI>Work with your network people to get the best reliability of the network that you can
    <LI>Convert to a SQL Server (or Oracle or DB2) back-end - they very seldom go corrupt, and have all sorts of recovery tools in case of catastrophic failures[/list]Hope this gives you some ideas - you might also check out <post#= 132047>post 132047</post#> and <post#=152256>post 152256</post#> for some other threads that look at corruption issues. Finally, you might want to look at this Microsoft Best Practices Article.
    Wendell

Posting Permissions

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