Attachments grow database although type is "Linked", not "Embedded"

[tzoykas]

Hello

I have a database that contains a table with an attachment field in it. The intent is to save pictures of objects in the database. I have a form that I use to add records to that table. There is an attachment control in the form in order to do that. I like very much the functionality of the control (browser that pops up to add a file, immediate display of picture, etc.). This control has a property "picture type", that can take three distinct values: "Embedded","Lin ked" and "Shared". From what I understand the "Embedded" option is to be avoided since it would add to the database, the size of the jpeg file (which it does). From what I read (and I couldn't find any concrete info on the options or the attachment datatype handling), linking the pictures should do the trick and just attach a file by saving the path, instead of saving the bitmap. However, it does exactly what "Embedded" does. It increases the size of the database by the filesize of the jpeg. What's more, "Shared" doesn't seem to have any effect either. All three options do exactly the same and that is to increase the database size by the filesize of my picture. Am I doing something wrong here?

I would like to avoid the "workaround " method that I have been reading about (with a text field that saves the path, and VB code to manipulate the picture display).

I am using Access 2010

Thanks in advance
George

[NeoPa]

I would guess that using the database will cause the space to be used up, but not necessarily on a permanent basis. If you do a Compact and Repair afterwards, does the size reduce again?

[tzoykas]

I would guess that using the database will cause the space to be used up, but not necessarily on a permanent basis. If you do a Compact and Repair afterwards, does the size reduce again?

Unfortunately not, I have already tried that.

[NeoPa]

That surprises me. I can't say I work too much with pictures and what I do with them uses your workaround approach anyway.

It really seems there's little point in using the Linked option at all if all you say is true.

[TheSmileyCoder]

I recommend foregoing the attachment field altogether for all but the very simplest of single user databases.

In Access 2010 you can bind a image control to a text field, where the text field contains the image path. The image control will automatically load the image (provided the path is valid) and this even work for continues forms, something I believe the workaround could not handle.

If you require more assistance please let us know.

[NeoPa]

Sounds like a real solution Smiley :-)