Embedding involves creating the image\/file directly using the associated OLE Server application.\u00a0 For example, if I choose to embed a bitmap image, Access will open Paint for me to create my bitmap image, and save that image into that field.<\/p>\n
![\"\"](\"http:\/\/www.yohz.com\/blogs\/wp-content\/uploads\/2017\/11\/ole_image_01.png\")
<\/p>\n
![\"\"](\"http:\/\/www.yohz.com\/blogs\/wp-content\/uploads\/2017\/11\/ole_image_02.png\")
<\/p>\n
- \n
- insert from a file<\/li>\n<\/ul>\n
If you already have the image\/file you want to store in your database, you can insert the file into your Access database directly using the Create from File<\/strong> option.\u00a0 Access then copies the file into the field.<\/p>\n
![\"\"](\"http:\/\/www.yohz.com\/blogs\/wp-content\/uploads\/2017\/11\/ole_image_03.png\")
<\/p>\n- \n
- link to a file<\/li>\n<\/ul>\n
Similar to the above, but this time, the image\/file is not stored in the database.\u00a0 Access just creates a link to the external file, much like a hyperlink in your browser.<\/p>\n
![\"\"](\"http:\/\/www.yohz.com\/blogs\/wp-content\/uploads\/2017\/11\/ole_image_04.png\")
<\/p>\nIf you store your images\/files using the first 2 methods, then Microsoft Access adds additional data to your image\/file, so that it knows which application to use to open that particular image\/file.\u00a0 This means that if you extracted the data from your database, it will appear different from your original file.<\/p>\n
For example, let’s insert an image into an OLE Object field.\u00a0 The image file is 18.7 Kb in size.<\/p>\n
![\"\"](\"http:\/\/www.yohz.com\/blogs\/wp-content\/uploads\/2017\/11\/ole_image_06.png\")
<\/p>\nOnce inserted into the Access database, the size has increased to 19.192 Kb.<\/p>\n
![\"\"](\"http:\/\/www.yohz.com\/blogs\/wp-content\/uploads\/2017\/11\/ole_image_07.png\")
<\/p>\nThe increase is due to the additional data added by Access.\u00a0 If you now extract the data as is from the database, it cannot be opened by Paint because of the additional data.\u00a0 The PNG data is preceded by OLE headers.<\/p>\n
This is a common issue faced by Microsoft Access users – when they want to extract images and files from OLE Object fields\u00a0to their original format, there isn’t a way they can do this easily.\u00a0 Every image\/file has been modified by Access.\u00a0 You have to open each image\/file in Access, then save the item to disk manually.<\/p>\n
This is the reason we created Access OLE Export<\/a>.<\/p>\n
![\"\"](\"http:\/\/www.yohz.com\/blogs\/wp-content\/uploads\/2017\/04\/aolescreenshot.png\")
<\/p>\nIn just 4 simple steps<\/a>, Access OLE Export<\/a> will extract and export your embedded images and files to disk, stripping out the additional data added by Access.\u00a0 The exported images and files can then be opened ‘normally’, using the appropriate application.<\/p>\n
If you require more control over what is exported, SQL Image Viewer<\/a> is another option.\u00a0 SQL Image Viewer allows you to inspect your data before exporting them, but requires that you be able to write SQL scripts.<\/p>\n
![\"\"](\"http:\/\/www.yohz.com\/blogs\/wp-content\/uploads\/2017\/04\/sivscreenshot.png\")
<\/p>\nThere may be situations where both products are unable to identify embedded images\u00a0correctly. \u00a0This may be because the registered OLE Server for that content type is not yet supported. \u00a0In these cases, send us (at\u00a0support@yohz.com<\/a>) a sample of the embedded data, and we will add support for that OLE server type.<\/p>\n
Download a FREE 14-day trial of Access OLE Export<\/a> or SQL Image Viewer<\/a> now to extract embedded objects from your Access databases the easy way.<\/p>\n
If instead you need to insert or update OLE-Object data in your databases, have a look at Access OLE Import<\/a>.\u00a0 Using Excel spreadsheets as the input data, you can easily add and update your embedded or linked OLE-Object data.<\/p>\n
You can purchase our products on this\u00a0page<\/a>.<\/p>\n
See also:<\/p>\n
- link to a file<\/li>\n<\/ul>\n