Reset form picture to nothing?

I accidently set this property to a picture, and I didn't want to. How to I reset it to nothing without doing it in code?

OK, Ill admit it ... when this happens to me I just paste some gray back into it to replace the picture.

I'm not sure if there is a more proper way of doing it.

Whew, thought I was the only one...lol.

I feel like I am going to have to cut and paste everything into a new form just to undo this. Seems like a harsh punishment for such a small mistake.

Anyone have a clue on how to do this?????

couldn't you just do form1.picture = loadpicture(""), or would that now work??

Quote:

---

Originally posted by Skitchen8
couldn't you just do form1.picture = loadpicture(""), or would that now work??

---

It should...

-C

Yes, but that would be in code, and that means that the picture is still going to be with the exe when I compile it. I don't like that. I am sure there is some way to do this without code.

oh, at design time when you click next to picture in the properties box (don't hit the ... thing) then hit either delete or bckspace, not sure which one.

Awesome,

I no longer have to live in shame when I make this mistake :p

I did check though, and the picture only stays with the project as part of the form. So if you had a 5 Mbyte picture the form would be about 5 Mbyte.

However, if you pasted a gray patch over it, it would be replaced and the form size would be back to around 1 Kbyte.

All kind of a moot point now, but it does make me feel better about past bloopers.

:D

Another way you could fix this problem would be to simply open your .frm file in Notepad and edit it. It's plain text so you can figure it out easy enough.

Knowing this can be useful for other "mishaps" as well :)

Thanks for your help guys, it is so simple that it makes me mad I didn't get it to work. All you have to do is highlight the (bitmap) part in the picture property, then hit the delete key.

Thanks

Hi Hellswrath
Yeah it is actually quite easy in VB6 but this was a known problem in earlier versions of VB so u are not the first to fall foul of it. In VB3 it was almost pot luck as to whether the delete process would work. Microsoft had unwittingly created a random number generator :p
Regards
Stuart