Ghost references to deleted tables in a back end database (Access2000 XP)


J

JHB

Hi:

I have an Access applications (2000 running under XT) where I have
split the database, and now have two files "TASC.mdb" and
"TASC_be.mdb".

I want to move the database "TASC_be.mdb" to another drive, which is
shared with others to make it a shared application. All this can
usually be done easily using the "Linked Table Manager". However I
have run into a snag. Since I split the database I have made a number
of changes and in the process have deleted a number of tables from the
be database. Now, when I copy the database to the new drive and try
and redirect the links (from "TASC.mdb"), I get questions about
linking up with some of the tables I deleted. These tables no longer
exist, but somewhere there appear to be references to them somewhere.

I have a feeling that the "ghosts" may have been created when I
opened the backend without the front end and deleted the tables, but
I am not certain about that.

I have two questions:

1. How do I get rid of these "ghost" references so that I can move
the database?
2. What is the CORRECT way to delete tables from a backend database
so that "Ghost" references are not created?

Thanks in advance for your help

John Baker
 
Ad

Advertisements

D

Douglas J Steele

Were the corresponding linked tables in the front end deleted as well?


"JHB" wrote in message

Hi:

I have an Access applications (2000 running under XT) where I have
split the database, and now have two files "TASC.mdb" and
"TASC_be.mdb".

I want to move the database "TASC_be.mdb" to another drive, which is
shared with others to make it a shared application. All this can
usually be done easily using the "Linked Table Manager". However I
have run into a snag. Since I split the database I have made a number
of changes and in the process have deleted a number of tables from the
be database. Now, when I copy the database to the new drive and try
and redirect the links (from "TASC.mdb"), I get questions about
linking up with some of the tables I deleted. These tables no longer
exist, but somewhere there appear to be references to them somewhere.

I have a feeling that the "ghosts" may have been created when I
opened the backend without the front end and deleted the tables, but
I am not certain about that.

I have two questions:

1. How do I get rid of these "ghost" references so that I can move
the database?
2. What is the CORRECT way to delete tables from a backend database
so that "Ghost" references are not created?

Thanks in advance for your help

John Baker
 
J

JHB

Were the corresponding linked tables in the front end deleted as well?

"JHB"  wrote in message


Hi:

I have an Access applications (2000 running under XT) where I have
split the database, and now have two files "TASC.mdb" and
"TASC_be.mdb".

I want to move the database "TASC_be.mdb" to another drive, which is
shared with others to make it a shared application. All this can
usually be done easily using the "Linked Table Manager". However I
have run into a snag. Since I split the database I have made a number
of changes and in the process have deleted a number of tables from the
be database. Now, when I  copy the database to the new drive and try
and redirect the links (from "TASC.mdb"), I get questions about
linking up with some of the tables I deleted. These tables no longer
exist, but somewhere there appear to be references to them somewhere.

I have a feeling that the "ghosts" may have been  created when I
opened the backend without the front end and deleted the tables,  but
I am not certain about that.

I have two questions:

1. How do I get rid of these "ghost" references so that I can  move
the database?
2. What is the CORRECT way to delete tables from a backend  database
so that "Ghost" references are not created?

Thanks in advance for your help

John Baker

Yes. There is no obvious reference to these tables in either the front
end or the back end! They do NOT appear in the tables list for the
front end.

John
 
J

John W. Vinson

Yes. There is no obvious reference to these tables in either the front
end or the back end! They do NOT appear in the tables list for the
front end.

I would suggest checking the frontend and turning OFF the "Name Autocorrect"
property - unaffecionately known as "Name Autocorrupt" by some of us. Compact
and repair the database and see if doing so exorcises the ghosts.

The next step would be to create a brand new, empty database; use External
Data... Link to link to the current backend tables; and then External Data...
Import to import all your queries, forms, reports and code (NOT the tables!).
--

John W. Vinson [MVP]
Microsoft's replacements for these newsgroups:
http://social.msdn.microsoft.com/Forums/en-US/accessdev/
http://social.answers.microsoft.com/Forums/en-US/addbuz/
and see also http://www.utteraccess.com
 
J

JHB

I would suggest checking the frontend and turning OFF the "Name Autocorrect"
property - unaffecionately known as "Name Autocorrupt" by some of us. Compact
and repair the database and see if doing so exorcises the ghosts.

The next step would be to create a brand new, empty database; use External
Data... Link to link to the current backend tables; and then External Data...
Import to import all your queries, forms, reports and code (NOT the tables!).
--

             John W. Vinson [MVP]
 Microsoft's replacements for these newsgroups:
 http://social.msdn.microsoft.com/Forums/en-US/accessdev/
 http://social.answers.microsoft.com/Forums/en-US/addbuz/
 and see alsohttp://www.utteraccess.com

Sadly the first option did not work and ghosts remain. The second
option sounds a bit drastic, and I have a few questions about it:

As I read it, I end up with three files (databases). One of the new
file containing the original Tables, the new set of tables Linked to
the original ones a then a new "front end" containing all the rest. In
other words I now have three files to work with all the time.Have I
missed something?

Would it be worthwhile JUST trying the external import approach and
creat a new front end , since I think the problem is is that the
ghosts lurk in the front end which somehow thinks the files exist. As
I said, I removed the tables from the BACK end directly and not
through the front end (which I now realize is the correct way).

I would appreciate your thoughts, since it could become quite a task!

Regards

John Baker
 
Ad

Advertisements

J

John W. Vinson

Sadly the first option did not work and ghosts remain. The second
option sounds a bit drastic, and I have a few questions about it:

As I read it, I end up with three files (databases). One of the new
file containing the original Tables, the new set of tables Linked to
the original ones a then a new "front end" containing all the rest. In
other words I now have three files to work with all the time.Have I
missed something?

Yes. You have currently a frontend, haunted and possibly corrupt and a
backend, which is hopefully OK and contains only the tables. My suggestion was
intended to be that you import all that is of use from the current frontend,
relink to the backend, and DISCARD the old (now useless) frontend, sending the
ghosts to their eternal rest. So you end up with your current backend (still
OK) and a new, clean frontend (with everything that you need from the old
frontend).
Would it be worthwhile JUST trying the external import approach and
creat a new front end , since I think the problem is is that the
ghosts lurk in the front end which somehow thinks the files exist. As
I said, I removed the tables from the BACK end directly and not
through the front end (which I now realize is the correct way).

I would appreciate your thoughts, since it could become quite a task!

Importing anything into the existing frontend would almost surely leave the
problem unresolved.
--

John W. Vinson [MVP]
Microsoft's replacements for these newsgroups:
http://social.msdn.microsoft.com/Forums/en-US/accessdev/
http://social.answers.microsoft.com/Forums/en-US/addbuz/
and see also http://www.utteraccess.com
 
Ad

Advertisements


Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top