🚀 go-pugleaf

I doubt seriously if 80,000 AutoCAD drawings _can_ be inserted into an
Access database.

I don't have code for AutoCad, but you'll find code for programmatically
inserting images into OLE fields in the examples downloadable from
http://members.tripod.com/accdevel. You may have to modify it a bit for
Linked, but, as Turtle pointed out, Linking isn't as cheap as you may have
thought.

"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
>
>
>