Is late binding even an issue?

[Robin]

I have a Form with an Unbound OLE Frame that has it's Source Doc set as a
linked Word 2007.docx file. This word file is only used as an advertising
display on the form and subsequent report.

The word file does not receive or provide any data from/to the Access
Database. And the file is supplied at runtime installation into a
subdirectory to complete the link. Users are aware that it can only be
altered if they have a licensed version of word 2007 on their computers.

It shows properly on all the forms and reports thus far without creating any
errors or crashes on all of the target machines, currently none have office
2007 or word 2007 installed (We're working on that). When the form is
accessed at runtime and the frame is double-clicked, Word either opens if
they have Word 2007 and they are able to edit the form. Or it fails and does
not allow editing, but no crashes, just an error that indicates the user
cannot edit the information.

Program is distributed ACCDE/ACCDB using Sagekey Scripts, Install Builder
8.14.

The references are to:
Visual Basic for Applications
Microsoft Access 12.0 Object Library
Microsoft Office 12.0 Access Data Engine Object
Microsfot ActiveX Data Object 2.8 Library
Sagekey Security

I hope I am correctly assuming that I must not be using "Automation" in this
particular situation. Because I am not experiencing the horrible crashing
side effects I've read about in this group. I've not had to use any
CreateObject or GetObject functions to get to this level of functionality.

Please let me know if I've made a serious mistake here that will pop up in
the future.

Thank you,
Robin

 

[Guest]

Correct, late binding is not an issue.

Actually, your form is using OLE Automation, and it's not an issue.

If you aren't using some of those other references, like

Microsoft Office 12.0 Access Data Engine Object
Microsoft ActiveX Data Object 2.8 Library

You should get rid of them too.

Any references in the VBA reference list are potential problems
even if you don't use them, so you want to get rid of any that
you can.

If you had used a Bound OLE Frame with an embedded docx
file, you might have accidentally wound up with a Word Reference
as well, which also might potentially have caused a problem,
but there is nothing to fix here.

There is always the possibility that something will 'pop up in
the future', but there is nothing else you can or should try to do.

(david)

 

[Robin]

Thank you for your comments. I'll be deploying the "final" version today and
certainly didn't want any unexpected surprises. Unfortunately, the
additional references are required for some third party imaging controls.
But we've been testing beta versions for 3 months on a dozen or so machines
used daily and everything works great thus far.

Thank you,
Robin

 

[mabel]

I have a Form with an Unbound OLE Frame that has it's Source Doc set as a
linked Word 2007.docx file. This word file is only used as an advertising
display on the form and subsequent report.

The word file does not receive or provide any data from/to the Access
Database. And the file is supplied at runtime installation into a
subdirectory to complete the link. Users are aware that it can only be
altered if they have a licensed version of word 2007 on their computers.

It shows properly on all the forms and reports thus far without creating
any
errors or crashes on all of the target machines, currently none have
office
2007 or word 2007 installed (We're working on that). When the form is
accessed at runtime and the frame is double-clicked, Word either opens if
they have Word 2007 and they are able to edit the form. Or it fails and
does
not allow editing, but no crashes, just an error that indicates the user
cannot edit the information.

Program is distributed ACCDE/ACCDB using Sagekey Scripts, Install Builder
8.14.

The references are to:
Visual Basic for Applications
Microsoft Access 12.0 Object Library
Microsoft Office 12.0 Access Data Engine Object
Microsfot ActiveX Data Object 2.8 Library
Sagekey Security

I hope I am correctly assuming that I must not be using "Automation" in
this
particular situation. Because I am not experiencing the horrible crashing
side effects I've read about in this group. I've not had to use any
CreateObject or GetObject functions to get to this level of functionality.

Please let me know if I've made a serious mistake here that will pop up in
the future.

Thank you,
Robin