Carolyn

https://www.youtube.com/watch?v=YDu4iqlci30

I watched the video but had already done what he suggested and it is not working.  The problem I am having is with hyperlinks.  
Any other ideas

Hi Carolyn, Hyperlinks are not one of  Rick's favorite things. See if ShellEx will work for you. (It is in the code vault) I use it extensively. HTH  John

I changed the hyperlinks to OLE Objects, but when they are stored in the database, rather than as links, they cause the database to grow very large.  Is there any way to shrink the size of the database without linking the objects (we may be moving where the database is located at times, and having the objects linked makes this unmanageable

One thing that some people who needed to embed ole objects in their database have done is to create linked backend tables that strictly store ole objects so that their main data tables don't bloat and then you keep those backend tables either, if you have a split database, in the same folder as your backend tables, or, if not, in the same folder as your main Access file. Then if you move or copy your database to another location, you just copy those linked tables with it.

Unfortunately, increased file size is one of the biggest reasons why ole objects, embedded images, and other attachments in the database are discouraged. That, in addition to those types of objects are easier to become corrupted, especially over a network.

As for linking files, it might be easier to store your file locations in a table, including a root path, etc., if not under the same path as your database, so that you would only need to go to one form to manage the links and this would eliminate the need for storing ole objects.

Hi Carolyn Try ShellEX ! John