MSACCESS File get corrupted frequently!!

  • Is there any reason for msaccess db gets corrupted frequently.

    Some times just after the intalations!!!




    My Blog: http://dineshasanka.spaces.live.com/

  • It must be version conflict.

    If you create a mdb file in access 2000 and opens it up in Access 97 then  it creates problem.

     

  • Thankx fro the infomation.

    But I'm opening it via VB.




    My Blog: http://dineshasanka.spaces.live.com/

  • If the data is on a network and the connection is lost or interrupted while accessing, it will often corrupt the database.

  • I don't know why it happens, but I used to have this problem all the time with a couple of "split" databases where the forms, queries, reports were in a front end .mdb on the user's local computer and the tables were in a backend .mdb on a network share where they would get backed up automatically every night.  Every time there was the tiniest glitch in the network, the backend (the part on the network share, the really IMPORTANT part!) would be corrupted without warning. 

    I finally moved ALL Access databases to the user's local machines and the problem quit happening.  After that we had to rely on the users performing manual backups, but by then, they were so paranoid about loosing thier data that they did the backups religiously.  (Don't know how long that lasted, though!)   

  • Versions is a good place to stat.

    If any pcs are running different versions of access or different service packs you can have real problems.

    Watch out for 2000 and XP as these can croupt the VBA modules.

    2000 needs to be at SR3 to work with XP, also note that the problem is based on a dll that might be comming with and OutlookXP upgrade.

    If versions are OK.

    Then do you have memo fields, in your tables.

    IF this is yes then you need to compact and repair frequently, like every day.

     

  • This is a problem that we had frequently in our organization.  After we moved the data to SQL Server and linked the tables to Access, the programs seldom, if ever get corrupted.  When the data sat in an Access database it could get corrupted several times a week.

     

  • This is a major problem in access (Corruption) .. which happens when Data get corrpted (inserted wrong)

    So you have to compact and repair every week to rearrange the tables and to repair any erorrs.

    you have to transfer to SQL Server or MSDE (small version of SQL Server) .. it is best if you can ..


    Alamir Mohamed
    Alamir_mohamed@yahoo.com

  • Yes Alamir,

    But the problem is customers does not like to move to SQLSERVER because of the cost factor.

    And I heard this very much less in MSACCESS 2003 is it true?




    My Blog: http://dineshasanka.spaces.live.com/

  • if you have 5 customers or less using your program, you can use MDSE.

    MSDE is for free.

    MSDE is the Simplest VERSION of SQL SERVER. but it does not support Any vsual tools (you have to deal with it through OSQL cmd or Access Data Pages [ADP] )

    by the way I notice that Access 2000 is more stable than Access XP (2002) and Access 2003 in dealing with data over the network .. and also the Corruption is done less in Access 2000.

    I hope this help u.


    Alamir Mohamed
    Alamir_mohamed@yahoo.com

  • Can u give me any link to download the MSDE




    My Blog: http://dineshasanka.spaces.live.com/

  • here is the link of MSDE with SP3a included

    http://www.microsoft.com/downloads/details.aspx?familyid=413744D1-A0BC-479F-BAFA-E4B278EB9147&displaylang=en

    by the way you have to searh in http://www.microsoft.com for how to use it.

    I hope this help u


    Alamir Mohamed
    Alamir_mohamed@yahoo.com

  • I have lots of clients using access with the Jet engine, they all seem to work fine with the correct maintenance.  As I understand SQL and MSDE will also require a little maintenance if used it the same manner, lots of updates require you to defragment the tables, in access this is done with the compact and repair utility.

    The frequency of compacting is based upon how fragmented  you DB becomes form updates.  Some of my clients compact daily, some once a week, some never.

    I have users with over 2,500,000 records in access databases.  And databases with over 50 users.

    The real problem I have found is the use of memo fields, these seem to create problems, I try to stay away form these fields, when posibble.

    Switching to SQL or MSDE is a good Idea, but Access is still a great frontend tool and Jet does handle smaller databases with less work. As my clients pay for my time, this means less $ for them.

    Good Luck

Viewing 13 posts - 1 through 12 (of 12 total)

You must be logged in to reply to this topic. Login to reply