Don’t know if this has been resolved but in case it hasn’t here is something that might help.
The attached demo has a font, image and word document embedded in a table. Since they are in the table as long binary objects they do not bloat the database as much as OLE objects. Of course they do increase the size but it is just one-to-one with the size of the original file, a 50K font will bloat by 50K.
I can not test this under all Access versions and operating systems so if someone can fault it please let me know and I’ll try to fix it. I also can’t test bar-graph fonts so you’re on your own there.
To load a new long binary object…
Shift down start the database.
Go to the table and add the name of the file, with extension.
If it is a font, check RegisterFont.
Close the database.
Place a copy of the file in the same directory as the database.
Open the database and the file should be placed in the table.
When the database closes the file will be deleted and any fonts unregistered.
(This last point is important. If the user modifies the object while it is open those modifications will be scrapped when the database closes. If you need to modify the object then save it with a different name, close the database, re-name the saved file and re-start the database. That will put the changes back into the table.)
Font registration code by Fabrizio Ranieri...
http://www.mentalis.org/tips/tip068.shtml
Everything else you can blame me.
Hope that helps.
Regards,
Chris.
