🚀 go-pugleaf

"I figured that a link to the file would be considerably  smaller than
inserting the file itself."

That is incorrect.
When you link an object, the entire object gets inserted, along with
instructions for refreshing it.
So if anything, linking will be larger than inserting the file itself.

It sounds as if you and the client need to sit down and work out the
requirements of the project.
Does the client need to see the drawing embedded in your Access form or
report?
Or should it appear in a separate window?
Do they need to interact with the drawing from your database?  (open it in
its own application?)
If it's going to appear in a separate window, what will trigger this
display?  (a button? a hyperlink? OnCurrent event?)

Another important question:
    Do you need to be able to display multiple records (with pictures) at
the same time  on a form?

Once you have a picture of what the client wants, you can think more
specifically about how to provide it.

     - Turtle


"Collywobbles" <kbannon@+no-spam+iolfree.com> wrote in message
news:PJ9H7.11407$j22.23429@news.iol.ie...
> As I said, they want about 80,000 files inserted into or somehow openable
> from the database !
> The client has set up a database which lists the project name etc and
> whether drawings etc for that project were designed for that project. What
> the client wants is to give us the (AutoCAD) drawings and insert them into
> the database. I figured that a link to the file would be considerably
> smaller than inserting the file itself.
> Anyway, going back to your recommendation, I suppose that we could
recommend
> that the client use hyperlinks. But if they say no I guess we have a lot
of
> work to do!
> Thanks Turtle
> K.
>
>
> "Turtle" <macdermott@mindspring.com> wrote in message
> news:9sgk4r$rne$1@slb6.atl.mindspring.net...
> > With all due respect, I seriously doubt that you want to insert 80,000
OLE
> > objects into your file.
> > It's a common misconception that Access doesn't store linked files in
the
> > database object.
> > In fact, it does store the object AND a reference to its source so that
it
> > can be refreshed.
> > (For an embedded object, the link is not stored, so an embedded object
> > actually takes a little less storage space.)
> >
> > I'd urge you to consider redesigning the application so that you store
the
> > file path/name to the document in question, instead of the actual
> document.
> > If you make it a hyperlink, your client can open the document simply by
> > clicking on it.
> >
> > HTH
> >     - Turtle
>
>
>