G
George
Hello!
I noticed that the when we set the picture property of a button or another
control as embedded, it takes a lot of place.
Is there an explication that show why the Access file encrease in size by
more than the picture size (even if it is a bitmap, a format that is normaly
heavy)
Exemple:
An mdb without picture would take 4 MB
the same file with pictures would increase to 40 MB with only 400 KB of
pictures. In JPEG format.
Is it because Access uses a non efficient compression to include the image
file?
Thank you in advance for any suggestion!
PS: I know that I can set the picture to Linked, and the Access file will
not increase in size, but I cannot do that because I want to keep its
portability as easy as it is now.
I noticed that the when we set the picture property of a button or another
control as embedded, it takes a lot of place.
Is there an explication that show why the Access file encrease in size by
more than the picture size (even if it is a bitmap, a format that is normaly
heavy)
Exemple:
An mdb without picture would take 4 MB
the same file with pictures would increase to 40 MB with only 400 KB of
pictures. In JPEG format.
Is it because Access uses a non efficient compression to include the image
file?
Thank you in advance for any suggestion!
PS: I know that I can set the picture to Linked, and the Access file will
not increase in size, but I cannot do that because I want to keep its
portability as easy as it is now.