[AccessD] "Faked" replication

Hi Steven

Interesting observation about the gifs. I'll make a note on that.

/gustav

>>> Access will convert it prior to storing it which may cause an
> uncontrollable bloat <<

> I appreciate the input on this. You're right: I'd never seen this mentioned anywhere. When we were first entering test data we found that GIFs pasted into an OLE Object field caused the least
> bloat. Sure, the MDB increased in size by about double the actual GIF file size; but at least the number of colors was enough to give a good representation. Pasting in a JPEG or BMP caused more
> bloat. I'm pretty confident that we've reached an optimum solution insofar as how to store pictures.

> At first I was baffled by how Access treats graphics. If you looked at the datasheet containing the graphic field you would see the OLE field filled with the word "Picture" or, if memory serves,
> "Bitmap". I never did figure out under what conditions Access stored graphics as "Pictures" or as "Bitmaps". I gave up after a while and just went witht the brute force approach: which graphic file
> format takes up the least space in the MDB but still gives decent quality when the graphics are pasted into OLE fields? 256 color GIF was it.