Re: Join Split Database

Correction - I was able to compact and repair; it was when I tried to import
the tables that I got the message.

"Katherine R" wrote:

> I followed your instructions and everything appears to be just fine now.
> Thanks.
> But I have problem with a different db now. I tried to compact and repair
> the back end of this other db, and I'm getting the message "Microsoft Office
> Access has encountered a problem and needs to close. We are sorry for the
> inconvenience." So I've fixed one db, but messed up another. Can you direct
> me to a solution to this new problem?
>
> "Jeff Conrad" wrote:
>
> > "Katherine R" wrote in message:
> > news:FC62AE04-CB4E-40AB-B56B-55290BBD722F@xxxxxxxxxxxxxxxx
> >
> > > Wow - that was a quick response. Thanks so much. Sorry if this is a stupid
> > > question - and I'm not even sure how to ask it - but is it the front end or
> > > back end that I'm attempting to fix? I know the tables are in the back end
> > > but isn't it the front end that I compact & repair? If all goes well and I'm
> > > able to recover the corrupted db/table, should I have the users replace their
> > > copies of the front end or is it sufficient that the table is repaired in the
> > > back end?
> >
> > If all your tables are in the back end (this should be the case in most situations)
> > then it is the back-end we need to work on. The front end merely has links
> > to the data tables and so anything you attempt to implement on the front end
> > will not solve the corruption issue. The users *should* not need to do anything
> > with their front ends when everything is fixed. However, no harm will be done
> > by giving them a fresh FE copy either once the issue is resolved.
> >
> > Since other users are using this database this is what I would do:
> > 1. Have everyone completely log out of the FE databases.
> > 2. Double check through Explorer that the location of the BE does
> > not have any residual LDB (locking file) present.
> > 3. Make two copies of the BE file and place in separate folders on
> > your C drive so you can work on it without interruption.
> > 4. Best case scenario is the users will not need to use the database
> > when you are fixing it. If they *have* to use it, instruct them that
> > any changes they make between now and when it is fixed will be
> > lost. Tell them to keep a record of the changes they make so they
> > can re-do the changes when everything is working OK.
> > 5. Download and follow the instructions here:
> >
> > Jetcomp utility available at:
> > http://support.microsoft.com/?id=273956
> >
> > 6. If everything *appears* to be OK, test, test, and test some more.
> > 7. Create a new blank database, turn off Name AutoCorrect, and then
> > attempt to import all the data tables from the *fixed* file into this new
> > container. If all the tables come across OK then I think you should be
> > in good shape.
> > 8. Go back to the shared folder where the BE is placed on the server.
> > Delete the existing file. Make sure there is no locking file present. Tell
> > everyone to close everything.
> > 9. Copy your *fixed* BE into this shared folder. Hopefully everything
> > should be working again.
> > 10. Create two new folders on the server somewhere where you can
> > find them. Name them CorruptedBEFile1 and CorruptedBEFile2.
> > (Two is better than one)
> > 11. Take one of the copies of the old corrupted BE file and place a
> > copy in each of these folders. Rename the database file to:
> > CorruptedBEMay262005.mdb in each of the folders
> > 12. Place a copy of the *fixed* file as well into a new folder on the
> > server (FixedBEFile) and name it FixedBEMay262005.mdb.
> >
> > Hopefully you should be OK now.
> > Review the links I provided before as well because some of them
> > discuss ways to prevent corruption. Very important reading.
> >
> > --
> > Jeff Conrad
> > Access Junkie
> > Bend, Oregon
> >
> >
> >
.

Relevant Pages

  • Re: #Name? error
    ... Have you done a compact and repair, or a decompile followed by compact and ... What happens if you create another database as a test, keep it simple, use ... Jeanette Cunningham MS Access MVP -- Melbourne Victoria Australia ...
    (microsoft.public.access.forms)
  • Re: Form Dirty not firing
    ... also forces me to do a backup and compact and repair again. ... MISSING references. ... Database Utilites... ...
    (microsoft.public.access.formscoding)
  • Re: Invalid bookmark when entering data in a subform
    ... The compact and repair, decompile and compile, and importing into a new ... And here is a standard sequence to fix a problem database. ... Still in the code window, choose Compile from the Debug menu. ...
    (microsoft.public.access.forms)
  • help with corrupt database
    ... I read your post below in the hope of finding help with a database that's ... I can't run the compact & repair utility now - I just get the same error. ... Do you think this file is corrupt beyond repair then? ...
    (microsoft.public.access.tablesdbdesign)
  • Re: .dbx file
    ... Click on FILE FOLDERS> COMPACT ALL FOLDERS ... Database programs keep a copy of data entries even after deletion. ...
    (microsoft.public.windows.inetexplorer.ie6_outlookexpress)