Deleted Image displayed when in Runtime but not Full Access

[NDayave]

How Do,

I am using custom message boxes to make them much more aesthetically pleasing. On this form, there are 4 images for "Question", "Informatio n", "Critical" and "Exclamatio n".

I found the custom message boxes at http://blog.nkadesign.com/2008/ms-ac...x-replacement/ and edited it to fit my needs - Background colours, borders, etc as well as the Images displayed.

I changed the images to completely different ones, deleting the originals and embedding the new on the form. For easy compatibility with the coding they have the same names as the original images.


When I open the message boxes in a full version of Access, they display the new images but in the runtime, the old, deleted versions are displayed.


I don't have the old images stored on my PC anywhere and the new embedded images are the only images on the form.



Any Ideas?

[jimatqsi]

Perhaps this link will help. It seems to be related.

http://bytes.com/topic/access/answers/196530-problem-embedded-jpg-image

Jim

[NDayave]

No offence, but that link is totally unrelated.
I am using embedded bitmaps, not linked Jpegs.

My problem is that one image is displayed when I open the form in a full version of access, whereas when opened in the Access Runtime, an older image that has been deleted is displayed.


This is persistent. I can open the same file in runtime and full version and see completely different images over and over again.


I'll state it again, the problem is that an embedded image displays a deleted version of itself when opened in Runtime.

[NeoPa]

It may help to know how exactly you are using these new images. What type of controls are you using? How are the images referred to? Which properties utilised? etc. Is your custom message box a form set up to work that way?

Remember, from the other side of a forum we need more details than if we had the database in front of us, particularly for questions which are clearly beyond the level of beginner simplicity.

[NDayave]

I feel that I should make it clear that I am not changing any of the Images on the form. I am not deleting or inserting at any time. This concerns static, embedded images that should not be changing.


The custom Message Box is a form that is formatted on it's Load to meet the requirements specified in the code.


The 4 images are called "imgExclamation ", "imgQuestio n" etc. and are embedded bitmaps that are displayed regardless of database location or software installed on the computer. They are stored in the Form.


All 4 are on the form at all times and are made visible based on the criteria passed.


Everything works as it should when using the full version of access, the visible properties are correctly set and the relevant image displayed.


When using the runtime, everything runs as it should. The right "imgxxxxxxx " is displayed. It is just an older version of the image that I replaced for a better image with the same name to save changing the VBA.



If you still have the version of the database I sent you NeoPa (In this thread) you can have a look at the difference when running in and outside of the Runtime.

[NeoPa]

I think I have it at home still (not here at work). What's the name of the form I should be looking at?

[NDayave]

It is called "FormDialog " and utilises the modules "API_GetTextMet rics" and "Dialog".

In the version you have it should open whenever the dialog.box command is used, so if you try to close the Load/Save Mailing List form, Export the selected Mailing List etc.

If it doesn't open or seem to be functioning in an apparently normal fashion, I'll upload a different version.

[NeoPa]

What are you referring to when you say the runtime?

I've created a 2003 MDE which seems to work fine. I thought only 2007 had an associated runtime. What am I missing here?

[jimatqsi]

Neopa, what he is referring to is that Microsoft offers a free runtime version of Access so developers can create Access solutions and sell/distribute them to people who have not actually bought Office. Installing the runtime is completely free, but you lose some options, like debug and development mode. You can send your mde copy to somebody who has not bought Office if they installed the runtime version of Access. See http://office.microsoft.com/en-us/ac...001120886.aspx for more info.

Jim

[NeoPa]

Thanks Jim. I wish I'd known about this two weeks ago. I ended up doing something at work in Excel which I'd rather have done in Access. We live & learn.

I guess installing both on the same PC is not a good idea? I have the full package installed on all my PCs.

[NDayave]

There is apparently a command line switch to force operation in the runtime - Adding /runtime to the shortcut IIRC - but I have never been able to get it to work.

As for installing both on one PC, it is possible. You just need to specify which version you open files in. (Right Click -> Open With)

It can also be uninstalled separately as well.


If you can't use the runtime, here is the difference. Top is in Full Access (Displaying correct image) and bottom in the Runtime (Displaying the old Image I deleted when making the form).

It is the same picture displayed using the same code on the same form. I have tried replacing the images but the problem persists.

[NeoPa]

Very strange really. These are both images you've added into the database yourself at one time or another it seems. I was originally understanding the issue as your replacing an inbuilt image of the buttons (IE the ones associated with vbExclamation, vbcritical etc).

I can't do any checking from here (work again), but as a shot in the dark, I'd suggest doing a Compact and Repair before whatever else you do to prepare it for the runtime. It may well prove a dead-end, but probably worth a try if you haven't already.