Using images in Access 2013

[klnlsu]

Has anyone had trouble using .JPG images in Access 2013 reports? I inserted some images (of arrows) onto a label report. Since then, I've had problems with my DB becoming corrupted or "unstable". I can give more detail if wanted, but my main question is do y'all recommend using images in reports and forms. If so, what format? Thanks!

[ItsMe]

I have not used 2013 to develop apps yet. I have used it for testing apps and that is it. As for an image control corrupting an Access file, no, I have not experienced that. I do not even recall having a corrupt image control. Although, I typically delete the image control if I am changing (while developing the app) from one size of an image to another.

As for file format, I use whatever. I try to match the resolution of the image with the function of the report. I will user higher resolution when exporting to PDF. I will user lower resolution (to match the printer's capabilities) when sending to the printer. I do not use Print Preview for Reports. If I did, I would match screen resolution for Print Preview.

[NTC]

While I use 2013 all the time these days - do not recall any app with images in the report. The general rule of thumb is that images should be stored in a folder outside the database because their file size just bogs down a database - and what occurs is that you set up a link to it which calls in the image when the display occurs.

This more involved approach isn't needed for a single simple image such as a logo - in which case one use the simple image control and insert it - and that's it. I put in logo jpegs all the time in forms/reports and don't have a problem.

So if you are talking about a single image - be sure you are using the correct image control (there is more then 1). If you are talking about lots of images then you want to set up a link approach.

And one thing that occurs to me whenever flaky behavior involves a report - the report is affected by the printer driver software even when printing is not taking place. So sanity check your situation on a different PC if possible - if it is ok on a different PC then that might indicate an issue involving the printer driver though I don't want to send you on that route unless everything else has been reviewed.....