B
BruceM
My situation is that I have a report that is to contain graphics that are
facsimiles of signatures. I know that storing graphics increases the file
size, but the graphics files are quite small (20 - 30 KB). I realize that
Access creates an extra version of stored graphics or something like that,
so the file size increases by more than the 20 KB for each picture, but the
database file size is still prettty reasonable.
There are two reasons why I would consider storing the graphic in a table.
It would be stored once in a single table, by the way, not in multiple
records. One is that I can't figure out how to link to the graphic. If I
link, do I store the link as a Hyperlink field, or what? How do I get the
linked graphic to appear on the report? Bound object frame or what?
The second reason I would consider storing the graphics is that there are to
be changes to our network, and linked objects may very well be in a
different location in the future, meaning that I would have to redefine all
of the links.
Any suggestions on how to proceed?
facsimiles of signatures. I know that storing graphics increases the file
size, but the graphics files are quite small (20 - 30 KB). I realize that
Access creates an extra version of stored graphics or something like that,
so the file size increases by more than the 20 KB for each picture, but the
database file size is still prettty reasonable.
There are two reasons why I would consider storing the graphic in a table.
It would be stored once in a single table, by the way, not in multiple
records. One is that I can't figure out how to link to the graphic. If I
link, do I store the link as a Hyperlink field, or what? How do I get the
linked graphic to appear on the report? Bound object frame or what?
The second reason I would consider storing the graphics is that there are to
be changes to our network, and linked objects may very well be in a
different location in the future, meaning that I would have to redefine all
of the links.
Any suggestions on how to proceed?