OLE Field

[mstorer]

OLE Got Me In Deep

I created a small database containing an OLE field for one user. Unfortunately, the one user turned into a department and now I have a 575 record, 1.4GB database that I am afraid will imminently crash. I am in the process of manually moving the files into a directory and creating hyperlinks (something I knew I should have initially done!)

Is there any way to automate this process so that the OLE object is exported into the directory and saved as the ID number of the record? I have a feeling I will need to open the OLE, Save As into the directory, then insert the hyperlink into the hyperlink field I added to the table.

I knew better than to use OLE fields, so I guess this is my punishment!

- Matt

 

[GumbyD]

You made the fatal error of trying to store these OLE objects in Access (sadly Access saves these objects as BLOBs - binary Large Objects). I have delt with this by storing the OLE objects in a seperate directory and the path in Access as a text field. When you want to display or print out the OLE objects you have a dummy picture or object in place on the form or report and you update the "Picture" property and with the path in code (either on a button push or set with an event property). Getting the OLE objects out will get your database done to a normal size too. I have seen databases go from 1 gb to 20 mb just by removing the OLE objects.

Good Luck

GumbyD