Whenever I try to backup my database or compact it, I get the
"Microsoft Access has encountered a problem and needs to close" deal
with the option to repair. When I attempt to do that, it tries to
backup the database and I get the same thing over and over.

In addition, whenever I try to export or copy my main table, which is
"tblGuest", it corrupts my database and then I get an error message
saying my file is no longer an Access database.

Any suggestions?

Make backups.

First try creating a blank database and importing all of the objects
from the suspect version. Compact, test, and try to recreate the
original problem. This may put you in the clear.

If not, try decompile. check here for help http://allenbrowne.com/tips.html

If you can't make that work you might search microsoft for jetcomp.exe

And if that doesn't work there are several comercial ventures that
will try and recover your application. I don't have a preference
there.

Good luck

tim mills-groninger

On Mar 7, 2:46*pm, RussCRM <srusskin... (AT) gmail (DOT) com> wrote:

To add to Tim's advice, you've identified tblGuest as the problem table, so
you probably want to focus on that table.

After making a backup copy of the file, open the relationships window and
delete any relationships between that table and others. Then open tblGuest
in design view. Open the Indexes box (toolbar, in table design view), and
delete all the indexes inluding the primary key index. Note: *DON'T* delete
the actual field: just the index.

If you can save the changes, try creating a new (blank) database, and
importing just that one table, structure only. If that doesn't work,
manually create the table (same fields and properties) and link the table,
and use an Append query to populate the new table.

If that still fails, go back to your original tblGuest and delete any memo
fields from the table. Then try importing into your new table.

If that still fails after the indexes and memos are gone, scan the table and
see if you can see a bad row. If you can identify the bad row, you may be
able to import the *other* rows, as long as you don't refer to the bad one.
This kind of thing:
http://allenbrowne.com/ser-47.html#RowsShowDeleted

Once you get this one table imported into your new database, you can import
the other tables, and then create the relationships again.

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"timmg" <tmillsgroninger (AT) gmail (DOT) com> wrote

Make backups.

First try creating a blank database and importing all of the objects
from the suspect version. Compact, test, and try to recreate the
original problem. This may put you in the clear.

If not, try decompile. check here for help http://allenbrowne.com/tips.html

If you can't make that work you might search microsoft for jetcomp.exe

And if that doesn't work there are several comercial ventures that
will try and recover your application. I don't have a preference
there.

Good luck

tim mills-groninger

On Mar 7, 2:46 pm, RussCRM <srusskin... (AT) gmail (DOT) com> wrote: