Results 1 to 10 of 10
  1. #1
    2 Star Lounger
    Join Date
    Jan 2002
    Location
    Delta, Br. Columbia
    Posts
    116
    Thanks
    1
    Thanked 0 Times in 0 Posts

    D/B Corrupt? (2000)

    I have 2 shared databases one of which is split into apps and data. The split one is a job management d/b and it has linked tables from the combined one for purchasing info. The Purchasing d/b (not split) has linked tables from the Job d/b for valid job info. Security is in place on both d/b's both using the same security file. Record locking is in place on the edited records and in addition I have built further lock fields in so that user can lock entire Jobs (and all details) or specific P/O's (and all details) but only when editing them. If another user attempts to open a locked job then they get an appropriate Lock message.

    My problem is that sporadically the d/b appears to get corrupted in that a user (no specific one) will log on, do some work and log off. Then he will try to log on again and be told the d/b is corrupt and needs repairing. This is of course impossible unless there are no other users logged on. So all users are asked to log off and the 1 user goes back in and when the corrupt message appears and it asks whether the d/b should be repaired, he say yes and after that all is well again.

    2 questions

    1) Why can a user who does not have Administer privileges repair the d/b (or does Access allow this when it is truly corrupt)? It cannot be done in the ordinary course of events - I have checked.

    2) Any other ideas on what might cause the d/b to go corrupt?

  2. #2
    Plutonium Lounger
    Join Date
    Dec 2000
    Location
    Sacramento, California, USA
    Posts
    16,775
    Thanks
    0
    Thanked 1 Time in 1 Post

    Re: D/B Corrupt? (2000)

    Unless your unsplit database is tables only, I highly recommend that you split it, even if it seems a very simple app. Corruption is far more likely in the user interface, and you can minimize problems by separating the front end from the data. As to why the corruption? Are all the machines running the same build of Access, with the same service packs for Office and Jet? Is anyone using XP? That message may appear when you mix the two versions.
    Charlotte

  3. #3
    2 Star Lounger
    Join Date
    Jan 2002
    Location
    Delta, Br. Columbia
    Posts
    116
    Thanks
    1
    Thanked 0 Times in 0 Posts

    Re: D/B Corrupt? (2000)

    Many thanks Charlotte

    Yes the un-split d/b will be split. I was unable to do it (and test) before I went down to NZ. Presumably the different versions/builds question only refers to Office not the OpSys? As far as I am aware they are only running Office 2000 but they maybe patched to different levels. They are running different OpSys including NT / 2000 / XP. This may have given them different patch levels. I will have to check.

  4. #4
    Plutonium Lounger
    Join Date
    Dec 2000
    Location
    Sacramento, California, USA
    Posts
    16,775
    Thanks
    0
    Thanked 1 Time in 1 Post

    Re: D/B Corrupt? (2000)

    I'm talking about Office and Jet, but we saw an Access XP crash on some of our machines where Office 2003 was also installed that was cured by applying the WinXP SR-3 on the machines. <img src=/S/shrug.gif border=0 alt=shrug width=39 height=15> Try to get the most level possible playing field.
    Charlotte

  5. #5
    2 Star Lounger
    Join Date
    Jan 2002
    Location
    Delta, Br. Columbia
    Posts
    116
    Thanks
    1
    Thanked 0 Times in 0 Posts

    Re: D/B Corrupt? (2000)

    One ore question and then I can check out the client machines. How does one find out the version of the Jet Engine? Access - I know by Help and then About Access but the Jet?

  6. #6
    Bronze Lounger
    Join Date
    Nov 2001
    Location
    Arlington, Virginia, USA
    Posts
    1,394
    Thanks
    0
    Thanked 3 Times in 3 Posts

    Re: D/B Corrupt? (2000)

    The simple answer is, check the DAO DBEngine Version property:

    ? DBEngine.Version
    3.6

    This indicates DAO 3.6 is the version in use (I'm using ACC 2000), and the Jet version would be 4.0. If you need to determine the specific Jet Service Pack (SP) installed on the client machine, then it's more complicated. See MSKB article 239114:

    How To: Obtain the Latest Service Pack for the Microsoft Jet 4.0 Database Engine

    The article explains "How to Determine the Current Service Pack Level of Jet 4.0", which requires that you determine the version number of the Jet 4.0 DLL (Msjet40.dll). If you're using A2K or later, then the Jet version would be 4.0 (which corresponds to DAO 3.6). For some examples of code that can be used to determine file version info for the Msjet40.dll (or for other system files in general) (requires using Windows API) see this previous thread:

    <!post=Re: How to Return Jet Version Number? (a2k (9.0.6926) SP-3 Jet 4.0 SP-7),320132>Re: How to Return Jet Version Number? (a2k (9.0.6926) SP-3 Jet 4.0 SP-7)<!/post>

    HTH

  7. #7
    Super Moderator WebGenii's Avatar
    Join Date
    Jan 2001
    Location
    Redcliff, Alberta, Canada
    Posts
    4,066
    Thanks
    2
    Thanked 5 Times in 5 Posts

    Re: D/B Corrupt? (2000)

    This is really a sidebar question to this thread, but as I read it I started to wonder about the relationship between Jet and Access. I mean I understand that the db engine for Access is provided by Jet, however, in practical terms what does this imply for maintaining one's Access install? I've just been service packing my Access install without thinking about Jet - should I add Jet sp's to my to do list? And what about my users?
    Your thoughts would be welcome.
    [b]Catharine Richardson (WebGenii)
    WebGenii Home Page
    Moderator: Spreadsheets, Other MS Apps, Presentation Apps, Visual Basic for Apps, Windows Mobile

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

    Re: D/B Corrupt? (2000)

    In general, you should keep everything up-to-date. But either Windows Update or Office Update (I forget which of the two) should automatically suggest installing a new Jet service pack if available.

  9. #9
    2 Star Lounger
    Join Date
    Jan 2002
    Location
    Delta, Br. Columbia
    Posts
    116
    Thanks
    1
    Thanked 0 Times in 0 Posts

    Re: D/B Corrupt? (2000)

    I have finally got around to checking the customer computers (have been down with flu) and sure enough there is a bit of a mix. 1 machine running 2003, 1 running XP, the rest (14) running 2000 but 6 of them not patched to the SR-1 level. I am having them update their patch level to SR-1. As far as I could see all versions of Jet (looking at the the DAO version) were the same namely 3.6. The 2 users not running 2000 are infrequent D/B users at best and the problem seems to occur whether they are on or not. Could it be the SR-1 patch?

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

    Re: D/B Corrupt? (2000)

    See MarkD's reply a bit higher up in this thread about the DAO/Jet Engine versions. Access 2000, 2002 and 2003 all use DAO 3.6 and Jet 4.0, but there are different service packs for Jet 4.0. The references Mark posted will let you find out which service pack has been installed. The last numbered one was Jet 4.0 SP-8, but there has been an unnamed update after that in one of the Windows security patches.

    the final update for Office 2000 was SP-3. Especially when working in an environment with different Office versions, it is wise to update as far as possible.

Posting Permissions

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