Can't add Ole object when using Runtime

[scotthutchings]

I can't seem to get my database to let me add OLE objects when I installed through the package solution forcing it to use Run-Time Access. Is this something I can overcome or do I need another way of attaching documents to my database?

Thanks for your help!
Scott

 

[HiTechCoach]

I can't seem to get my database to let me add OLE objects when I installed through the package solution forcing it to use Run-Time Access. Is this something I can overcome or do I need another way of attaching documents to my database?

Thanks for your help!
Scott

Scott,

Are you using Access 2007 or 2010?

I prefer to link documents using this:

Document Links 2

 

[scotthutchings]

Thank you for your help. I am using Access 2007.

I finally figured out how to get this method to work in my database but when I presented it to my client they insisted that the file itself be stored in the database and not simply a link. They will be accessing the database from several different offices in different countries and cannot afford to have a broken link from a file that has been moved or deleted. I understand that this will create bloat to my database so I created a completely separate database to hold nothing by the project documents and link to this table. Can I use a similar method to store the actual file and not just a link to the file?

 

[HiTechCoach]

Thank you for your help. I am using Access 2007.

I finally figured out how to get this method to work in my database but when I presented it to my client they insisted that the file itself be stored in the database and not simply a link. They will be accessing the database from several different offices in different countries and cannot afford to have a broken link from a file that has been moved or deleted. I understand that this will create bloat to my database so I created a completely separate database to hold nothing by the project documents and link to this table. Can I use a similar method to store the actual file and not just a link to the file?

Just to see how much bloat is caused by OLE, I created a blank database in 2010 with a single table with a single field OLE field and a long integer like would be used as foreign key for linking

File size when empty 364kb

I inserted a PDF that is 128 kb

New accdb file size was 3376 kb after compacting.

That was over a 20 times bloat.

What will the user need to do with the documents that are stored in the database?