Acess Crashes when I try to delete a link to a table

  • Thread starter Thread starter dchendrickson
  • Start date Start date
D

dchendrickson

I am using Access2002/XP under XP Pro.

I have split my database application into a front
end/back end set up. I am the only one working on this
application, so as yet there is no security in the
database. The front end file and the back end file are
located in the same folder on the machine's local hard
drive.

Today I created a couple of new tables for some new
functionality. The tables were created in the front end.
Once I was satisfied with how they were working, I
exported them to my backend file, deleted from my front
end file, then created links to the tables from the front
end to the back end.

Later I found my design needed modification. I planned to
delete the links, then export the tables from my back end
back to my front end for (at least for me) easier
manipulation. Two of the file links deleted without
issues and the export from the back to the front occurred
without problems also. But when I try to delete the link
to my third table from the front end, Access asks if I
was sure I want to do that and then crashed when I click
OK. My definition of "crashed" is that Access put up the
generic XP message:

"Microsoft Access has encountered a problem and needs to
close. We are sorry for the inconvenience."

and then asked if I would like to file an error report.
Access then creates a backup of the crashing file and
reopens.

This has happened repeatedly. I have tryed to refresh the
link with the link manager. I have tried deleting the
table from the backend. I have tried creating a new
version of the table in the backend and refreshing the
link to the new table. Always the same result. I have
even rebooted my PC (which is a very stable box).

Any suggestions to get rid of this link. The table itself
is simple and contains no data so I have no qualms about
getting rid of it if the solution involves that.

Thanks.

-dc
 
Can we safely assume that you have done a compact and repair on both the FE
and BE?
 
If you are the only one working on the backend, I would not go through the
trouble of creating the tables in my FE and then exporting them to my BE and
then have to link inside the FE. Just make your tables directly in the BE.
The fact that your are going back and forth, you may be corrupting the
System tables within your FE to the point of possible permanent corruption.
 
Kevin,

Both have been compacted and repaired. I can still hope
that the issue is something simple and boneheaded on my
part...

Thanks for the suggestion.

-dc
 
GVaught,

As is probably obvious, I am a newbie as Access. I
creating in the FE and moving to the BE because Access
tells me I cannot edit the table design in the BE from
the FE. So is there a setting somewhere I can change that
will allow me to edit the table design from the front end?

Thanks,

-dc
 
All,

I still don't have a root cause or solution to fix this -
but I do have an uncorrupted backup. So I am functional
again. I still would like any ideas regarding a solution
though. Thanks.

-dc
 
It sounds to me like the exporting process is what's killing you here.
Perhaps Access is somehow getting confused by the fact that you once had a
table named "Table", which is gone, and now you have a link named "Table"
that you are trying to delete.

Create and modify your tables in the back-end as a workaround.
 
Back
Top