Getting Rid of Graphic Reference

[MIG]

I have a database converted from Access 97 to Access 2000. Some of the
forms used to display a linked graphic, which no longer exists.

When I switch from design view to form view, I get repeated annoying
messages about not being able to find the file.

When I go to the properties of the form detail etc, I cannot get rid of
the reference to the linked graphic (a bitmap). When I delete the
name, it just reappears when I leave the field. I might have expected
a question about confirming that I want to remove the graphic, but I
get nothing.

Has anyone got any ideas for how I might get rid of it?

Thanks.

 

[Brendan Reynolds]

I don't have a copy of Access 2000 installed on this PC to test this, but
try entering the text "(none)" (without the quotes) in place of the file
name.

 

[MIG]

I don't have a copy of Access 2000 installed on this PC to test this, but
try entering the text "(none)" (without the quotes) in place of the file
name.

Thanks, but no, that didn't work either. The filename just bounces
back. The ... button just leads to a browsing window (no choice of a
"none" or anything there).

 

[Brendan Reynolds]

I'm afraid I don't know what else to suggest. I just tried it on another PC
that does have Access 2000 (SR1) installed. Deleting the file name or
replacing it with (none) both work on that PC.

 

[MIG]

I am coming to the conclusion that it must be a conversion problem, as
in something got hard-coded in converting from 97. Maybe there's a
source of help specifically on conversion issues that I need to look
up.

<time elapses>

Ahaha. If I dig around and find any old graphic via the ... button, I
can insert that. Then I can delete that and I get the usual message
asking if I want to remove it, which I do, and then it's gone. Sorry,
I should have tried that sooner, but didn't have a graphic to hand.

I think it must have been due to the conversion initially though.

 

[Brendan Reynolds]

It doesn't seem to be a conversion issue, as I can now re-produce it in
Access 2003. The mistake I made earlier was that I tested only with a file
that actually existed. I can reproduce the behaviour you described if I set
the property, then move or rename the file. So far, the technique you
discovered - change to another file that actually exists and then delete or
change to (none) - seems to be the only solution.