database size

[Leo_Polla_Psemata]

Hi
On access 2016, i am designing a db which will need to store around 1000 records, one field will be "OLE OBJECT",
the size of its OLE will be around 300 KB, it will be a picture cropped from my pc screen using snipping tool.

How big is the bd going to be after 1000 records?
1000 ole objects of 300 kb eacj plus some short text data?

 

[CJ_London]

1000*300kb=approx. 300mb

to this you need to add the size of the other fields in the table, plus indexes.

see these links for data sizes

http://www.w3schools.com/sql/sql_datatypes.asp
https://msdn.microsoft.com/en-us/library/dd301350.aspx

 

[Ranman256]

If you need, you can always put the ole field in its own table ,in its own database.
KeyID,OleFld.

Link the table in and join to the main table. This can save space if you get close to 2 gig.

 

[jdraw]

Leo,
Have you considered storing the photos in the filesystem; and just putting a folder/file reference in the database? This would move the storage from the database and reduce actual database size.

 

[The_Doc_Man]

A note in point: If you take jdraw's advice of having a text reference to the file, in the general form of either "\\server\share-name\folder\...\folder\someone.JPG" or (if it is always on the same system that you are) "dev:\folder\...\folder\someone.JPG," then you need to use a form or report to actually view the picture because in this format, it is no longer an OLE object. It becomes just another external file. You might also have to use the File System Object library to invoke a "file picker" dialog to GET that specification. However, you can web-search that topic or forum-search it very easily.

I'll also add that jdraw's suggestion works fine. My family reunion photos are on a home database that does this. All that is needed is for a form's OnCurrent event or a report's OnPaint or OnPrint event to load the file spec from a short-text field (probably a long Short Text field, at least 64 bytes and 128 wouldn't hurt depending on folder name sizes) into the .Picture property (or is it .Image property? I never remember when shooting from the hip) of the Image control. The delay to access the object is negligible compared to the time it takes to paint pictures, particularly when using the scaling option in the image control. The only hiccup has to do with either case is whether there is a serious resolution mismatch in the stored image and the display or printer being used to render same, but that would even apply to OLE cases, so it isn't an issue with the method - it is an issue with images in general.