Access just threw me a huge curve ball. What's new, right? I've been converting a 2003 database to a 2007 database using the 2010 version of Access. Everything has been going great, until I started working on some reports with links to images I use to underlay the report. Basically, I have a large linked image, 7.5"x9.5" let's say, of a form that I then overlay with report data. I've been doing this forever and it has never been an issue. The average image size is about 1mb and I have two of them to a report, the front and back of the page. Simple stuff, right?
Everything worked as normal until I went to Print Preview. Only one of the pictures showed up in Preview. Thinking I just missed something, I checked it all over and it looked good. Tried again and the same result. After tinkering around a bit, I started thinking maybe it was a memory problem. I closed the app, reopened and tried again. Same result, but this time I checked the Task Manager and bam! When opening the report, Access's memory usage jumped from 70mb to over 450mb! It stayed that way until I closed the report. Sometimes it would show one picture, sometimes none and it would never actually print. Remember, this was the result of adding 2 b&w, text images at about 1mb a piece. Insane!
Ok, so I started playing with picture size. After compressing them down gradually, the memory usage also went down. Once I got down to about 200kb, things went back to normal, albeit a crappy compressed, unusable image. This still doesn't explain why it is happening in the first place. Doing the exact same thing in 2003, the same report even, only bumps the memory up a tad. About the amount of the picture size, which makes sense. Something has to completely out of whack with 2010. I noticed a couple other references to 2007 in other posts, so this must have started with that.
To further my research, I tested this on a couple different machines & operating systems and got the same result. Because Access, in my experience, can have sporadic results going from print driver to print driver, I also tested it using different default printers. Some made a difference, but it was still huge memory jump.
I can't be the only one who uses image backgrounds/underlays/overlays like this, so I can't believe I can't find more references to this problem. The couple I did find didn't provide any solutions. Based on my tests with multiple machines, it can't just be me.
Any thoughts would be appreciated.
I should add that doing this same thing in Access 2003, I have some linked images as big as 5-6mb and that is no problem either.