Results 1 to 8 of 8
  1. #1
    Join Date
    Mar 2009
    Location
    SLOVAKIA,Bratislava
    Posts
    70

    Lightbulb Unanswered: Repair-DB Error (Modules Container:....)

    Access 2003 (11.8166.8221) SP3,SINGEL USER,SECURE MDW, large database(NONE tables) 15 MB

    ? CompactRepair( "MyData.mdb","MyData_new.mdb",true)
    -------------------------------------------------------
    Log file (MyData_new.log)....corruption is there !!!
    Modules Container: 'DirDataCopy' stream has a length of zero!
    Modules Container: 'PropDataCopy' stream has a length of zero!

    Hi , how to repair it ?
    The same One-DB, when in 4-References DB than repair-log OK...
    Who knows the background of this Error ?
    eMail: jan.pacala@zoznam.sk
    15 years db-programmer(dBase,FoxPro,MS Access 2002/2003),Symbian C++

  2. #2
    Join Date
    Mar 2009
    Location
    SLOVAKIA,Bratislava
    Posts
    70
    File-MDb.log (CompactRepair LogFile:=true)
    Modules Container: ' DirDataCopy' stream has a length of zero!
    Modules Container: 'PropDataCopy' stream has a length of zero!
    MSysAccessStorage:
    Code:
    DateCreate      DateUpdate      Id      Lv      Name    ParentId        Type   
    04/03/2008 8:52:29      17/02/2009 14:19:00     13              Modules 1       1      
    13/02/2009 15:03:40     13/02/2009 15:03:40     210     Long binary data        PropData        13      2      
    13/02/2009 15:03:40     13/02/2009 15:03:40     211     <––– EMPTY –––->        PropDataCopy    13      2      
    13/02/2009 15:03:40     13/02/2009 15:03:40     218             3       13      1      
    13/02/2009 15:03:40     13/02/2009 15:03:40     221             4       13      1      
    13/02/2009 15:03:40     13/02/2009 15:03:40     224             5       13      1      
    13/02/2009 15:03:40     13/02/2009 15:03:40     227             6       13      1      
    13/02/2009 15:03:40     13/02/2009 15:03:40     233             8       13      1      
    13/02/2009 15:03:40     13/02/2009 15:03:40     239             10      13      1      
    13/02/2009 15:03:40     13/02/2009 15:03:40     242             11      13      1      
    13/02/2009 15:03:40     13/02/2009 15:03:40     257             16      13      1      
    13/02/2009 15:03:40     13/02/2009 15:03:40     260             17      13      1      
    13/02/2009 15:03:40     13/02/2009 15:03:40     263             18      13      1      
    13/02/2009 15:03:40     13/02/2009 15:03:40     266             19      13      1      
    13/02/2009 15:03:40     13/02/2009 15:03:40     275             22      13      1      
    13/02/2009 15:03:40     17/02/2009 14:19:00     287     Long binary data        
    
    
    --------------------------------------------------------------------------------
    DirData        13      2      
    13/02/2009 15:03:40     13/02/2009 15:03:40     288     <––– EMPTY –––->        
    --------------------------------------------------------------------------------
    DirDataCopy    13      2
    15 years db-programmer(dBase,FoxPro,MS Access 2002/2003),Symbian C++

  3. #3
    Join Date
    Mar 2009
    Location
    SLOVAKIA,Bratislava
    Posts
    70
    DB i can open and run.
    But sometimes they are problems
    -with compiler/Crash see other threads
    -After SaveAstext/LoadasText the same
    -compile on demand =OFF
    - When i build ONE-MDE, about 80-95 % is WRONG (Crash) and ~5-20% is really running near 100% O.K.
    The same when not ONE-MDE , but FOUR-MDE(through references-MDE)
    15 years db-programmer(dBase,FoxPro,MS Access 2002/2003),Symbian C++

  4. #4
    Join Date
    Mar 2009
    Location
    SLOVAKIA,Bratislava
    Posts
    70
    Access 2002 Desktop Developers Handbook (Litwin,Getz,Gunderloy)
    page: 984
    in previous versions of Access( we have not yet cnfirmed taht this happens with Access 2002, but it is worth knowing anyway), the VBA project for LARGE databases could, on occasion, become CORRUPTED.Weird things happen, and it is NOT CLEAR why things go wrong.
    If you find VBA behaving oddly, and you are working with large application, you may want to try the undocumented /DECOMPILE command line option,...
    15 years db-programmer(dBase,FoxPro,MS Access 2002/2003),Symbian C++

  5. #5
    Join Date
    Dec 2002
    Location
    Préverenges, Switzerland
    Posts
    3,740
    re:
    ? CompactRepair( "MyData.mdb","MyData_new.mdb",true)
    -------------------------------------------------------
    Log file (MyData_new.log)....corruption is there !!!
    Modules Container: 'DirDataCopy' stream has a length of zero!
    Modules Container: 'PropDataCopy' stream has a length of zero!


    can't explain it, but i'm pretty convinced it is NOT a pointer to a corrupt db. i can replicate this behaviour any time from A2K3 (in both A2K and A2K3 format) by adding the simplest module to an otherwise empty new db.

    e.g.

    make a new totally empty .MDB
    try application.compactrepair -- returns True and no logfile generated

    add a module "myModule" containing a single simple function such as
    Option Explicit
    Public Function myDate() As String
    myDate = Format(Now(), "YYYY-MM-DD")
    End Function
    NB the rest of the db remains completely empty

    now try application.compactrepair again -- returns True but generates a logfile:
    Modules Container: 'DirDataCopy' stream has a length of zero!
    Modules Container: 'PropDataCopy' stream has a length of zero!

    there's a bug in there somewhere, but it is not in your .MDB

    izy
    currently using SS 2008R2

  6. #6
    Join Date
    Mar 2009
    Location
    SLOVAKIA,Bratislava
    Posts
    70
    Microsoft-web-site:....???/!!!
    Access
    CompactRepair Method [Access 2003 VBA Language Reference]
    Compacts and repairs the specified database (.mdb) or Microsoft Access project (.adp) file. Returns a Boolean; True if the process was successful.

    expression.CompactRepair(SourceFile, DestinationFile, LogFile)

    expression Required. An expression that returns one of the objects in the Applies To list.

    SourceFile Required String. The full path and filename of the database or project file to compact and repair.

    DestinationFile Required String. The full path and filename for where the recovered file will be saved.

    LogFile Optional Boolean. True if a log file is created in the destination directory to record any corruption detected in the source file. A log file is only created if corruption is detected in the source file. If LogFile is False or omitted, no log file is created, even if corruption is detected in the source file.
    15 years db-programmer(dBase,FoxPro,MS Access 2002/2003),Symbian C++

  7. #7
    Join Date
    Dec 2002
    Location
    Préverenges, Switzerland
    Posts
    3,740
    and ?



    did you try the experiment ?

    izy
    currently using SS 2008R2

  8. #8
    Join Date
    Mar 2009
    Location
    SLOVAKIA,Bratislava
    Posts
    70
    Yes you are right ...
    When i create FOUR-MDEs from my One-DB, there is NONE logfile ?!!
    ---------------------
    How to repair DB ?
    But my opnion/expierience is to Repair DB NOT only One-times, but MORE times...
    When i create MDEs, i allways make two 'SAME' files. and it happens that
    one crashes and other NOT !!!!
    But more stabil is ONE-SINGEL-MDE(9.3MB) than Multi-MDEs
    (2,4MB+3,5MB+2,1MB+2,3MB)
    I have last year Reported to Microsoft about 500 Crashes !!!!, and nothing happens...
    15 years db-programmer(dBase,FoxPro,MS Access 2002/2003),Symbian C++

Posting Permissions

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