Loading a OLE field programmatically

[josekreif]

Been a long time since I was here. Hoping to get a resolution as usual

I'm moving an old Lotus Approach database over to Access since we have to replace this person's work PC and Lotus will not work on Windows 7+. The database keeps track of .dwg autocad drawings.

I don't want to force the user to load each field.

I assume if you have a set variable for the folder/path, and a field containing the name of file, you should be able to load them on the fly.

I just need the syntax

I assume it's similar to

.Edit
rst("myOLE") = "x"
.Update

[orange]

Sounds simple enough, let us know how it goes.

IIRC I think Lotus Approach used a dbase file structure ( you might be able to link to it using the dBase option)???(unsure)

[NTC]

Since this seems like a fundamental redesign, I would not necessarily stay with OLE nor would I load them on the fly; as then the image is opening even if the user doesn't care if they see it...but that image load is a task that takes time and will slow the application. I believe it is a better design in most cases, not necessarily all, to have the image as a link only - and then the user activates the image if they wish to see it - - and it opens in its native format in a window outside the database. This is a more robust design overall.

[josekreif]

Since this seems like a fundamental redesign, I would not necessarily stay with OLE nor would I load them on the fly; as then the image is opening even if the user doesn't care if they see it...but that image load is a task that takes time and will slow the application. I believe it is a better design in most cases, not necessarily all, to have the image as a link only - and then the user activates the image if they wish to see it - - and it opens in its native format in a window outside the database. This is a more robust design overall.

There doesn't seem to be another way to integrate .dwg files into Access. Not one I can see at this time.

If not store all them in a OLE field and use the bound object in form, I would use a unbound to load them as user enters the record on form.

Sounds simple enough, let us know how it goes.

IIRC I think Lotus Approach used a dbase file structure ( you might be able to link to it using the dBase option)???(unsure)

I'm sorry if I wasn't clear.

I'm actually asking the question "How do I Load a OLE programmatically"

[NTC]

my knowledge of autocad is superficial but you are correct in there not being an easy way to integrate .dwg files into Access so to speak; and OLE in general has some issues in terms of performance. So because of this I was suggesting an approach whereby the database's role is to hold the link/path to the .dwg files and nothing else. this is very efficient in terms of the db performance. One method is to use a hyperlink field type. Then when the user activates that hot link one relies on Windows (not Access) to launch the native default application. For bigger more complex applications like AutoCAD - - which includes Adobe, Word, Excel - - this is a better way to go. Attempting to window these apps inside an Access database generally is a non starter.

for smaller static images in jpg, bitmap type formats - such as driver license scans or something - - one would still hold the image file in a folder outside the database - - and then use an image control in a form/report to display the image...but I consider autocad to be a much bigger application overall and if those file sizes are large you don't want them auto loading into the database particularly if the person may not even need to see them - better to have them instead be on demand and open in a separate window.