Hi JK,
The increase in file size that you witnessed for the 422 KB embedded .jpg
file, 5068 KB (= 4.95 MB approx.) is due to the method that Access uses to
embed images. My understanding is that images get converted internally to
..bmp format. Apparently the next version of Access, currently in beta
release, has finally solved this problem. You can read more about it at this
link:
http://blogs.msdn.com/access/archive/2005/11/07/490113.aspx
which includes the following quote: "Modern image support - use png, gif,
jpg, etc without database bloat and maintain transparency."
Your 113 KB letterhead .bmp file was already in the .bmp file format, so the
resulting 132 KB growth is much more reasonable by comparison. The bloating
is certainly proportional to the resolution and file type of the source image.
2. For permanent images such as logo I don't like linking because the file
can be renamed, moved or deleted.
I volunteered the linking, since the OP included the word linking in his
original post. I have not yet investigated if it is possible to set the
linked path at run-time. If it is, then this could help with the issue that
he mentions in the follow-on post (8:46 AM PST): "I do my enhancements on my
home pc and the db sits on the server at work." Certainly embedding is
easier, and you're always guaranteed to have the file available, as long as
you are willing to deal with any bloat issues.
Tom Wickerath
Microsoft Access MVP
http://www.access.qbuilt.com/html/expert_contributors.html
http://www.access.qbuilt.com/html/search.html
__________________________________________