I have an database that uses msoutl.olb, the outlook object library for the
date() objects. It also uses some object from the word library.
I have bought Office 2007, for the sole purpose as to be able to create the
runtime version of my database.
Now it seems that the database can obnly work on systems that do have ms
word and ms outlook installed.

is there any way to compile the office objects into the run time version of
the database?

Thanks in advance for your answer,

Dr. M.C. Koops

Not only is it not possible to compile Office objects into an Access
application (regardless of where you're using the run-time), distributing
files like msoutl.olb is illegal.

--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no private e-mails, please)


"Dr. Koops" <Dr. (E-Mail Removed)> wrote in message
news:ACEDDFA3-3C12-4FCE-B334-(E-Mail Removed)...
>I have an database that uses msoutl.olb, the outlook object library for the
> date() objects. It also uses some object from the word library.
> I have bought Office 2007, for the sole purpose as to be able to create
> the
> runtime version of my database.
> Now it seems that the database can obnly work on systems that do have ms
> word and ms outlook installed.
>
> is there any way to compile the office objects into the run time version
> of
> the database?
>
> Thanks in advance for your answer,
>
> Dr. M.C. Koops

"Douglas J. Steele" wrote:

> Not only is it not possible to compile Office objects into an Access
> application (regardless of where you're using the run-time), distributing
> files like msoutl.olb is illegal.

I understand that, but is it not possible (and legal) to reference the
msoutl.olb that's already on the user's sytem if they have Office/Outlook
already installed? For instance, I'm developing with Access XP (ACC10) so
the Outlook Object Library is located here:

c:\Program Files\Microsoft Office\Office10\msoutl.olb

I'm assuming that if my application is installed on a system that has
Outlook XP already installed it will run "out of the box" if it finds
msoutl.olb in that subdirectory, right? (Btw, I'll be distributing my
application as an MDE front-end and an MDB back-end, in case that makes a
difference?)

This brings up another question... If the user has Access/Outlook 2003 or
2007 installed, is it possible to programmatically search for msoutl.olb on
their system, change the reference to point at that library, and have the
application run properly? Or, will my application *only* run on an
Access/Outlook XP (2002) system? (Btw, I'm assuming that my application will
*not* run on anything earlier than Access/Outlook XP, right?)

If the answer to that last question is that it will run so long as the
reference is changed, can someone explain how to programmatically change the
reference? I'm assuming that'd be a DAO routine, right?

Thanks, in advance, for any advice and assistance given.

Regards, Chris

Chris O''''Neill wrote:
> "Douglas J. Steele" wrote:
>
>> Not only is it not possible to compile Office objects into an Access
>> application (regardless of where you're using the run-time),
>> distributing files like msoutl.olb is illegal.
>
> I understand that, but is it not possible (and legal) to reference the
> msoutl.olb that's already on the user's sytem if they have
> Office/Outlook already installed? For instance, I'm developing with
> Access XP (ACC10) so the Outlook Object Library is located here:
>
> c:\Program Files\Microsoft Office\Office10\msoutl.olb
>
> I'm assuming that if my application is installed on a system that has
> Outlook XP already installed it will run "out of the box" if it finds
> msoutl.olb in that subdirectory, right? (Btw, I'll be distributing my
> application as an MDE front-end and an MDB back-end, in case that
> makes a difference?)
>
> This brings up another question... If the user has Access/Outlook
> 2003 or 2007 installed, is it possible to programmatically search for
> msoutl.olb on their system, change the reference to point at that
> library, and have the application run properly? Or, will my
> application *only* run on an Access/Outlook XP (2002) system? (Btw,
> I'm assuming that my application will *not* run on anything earlier
> than Access/Outlook XP, right?)
>
> If the answer to that last question is that it will run so long as the
> reference is changed, can someone explain how to programmatically
> change the reference? I'm assuming that'd be a DAO routine, right?

Search these groups for "Late Binding". It accomplishes exaclty what you
are describing although not in the manner you describe. It is the only
practical way to use external libraries in a distributed app. Basically it
is a way to utilize external code libraries without setting a reference to
them.

--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com

"Rick Brandt" <(E-Mail Removed)> wrote in message
news:8nYjk.13778$(E-Mail Removed)...
> Chris O''''Neill wrote:
>>
>> This brings up another question... If the user has Access/Outlook
>> 2003 or 2007 installed, is it possible to programmatically search for
>> msoutl.olb on their system, change the reference to point at that
>> library, and have the application run properly? Or, will my
>> application *only* run on an Access/Outlook XP (2002) system? (Btw,
>> I'm assuming that my application will *not* run on anything earlier
>> than Access/Outlook XP, right?)
>>
>> If the answer to that last question is that it will run so long as the
>> reference is changed, can someone explain how to programmatically
>> change the reference? I'm assuming that'd be a DAO routine, right?
>
> Search these groups for "Late Binding". It accomplishes exaclty what you
> are describing although not in the manner you describe. It is the only
> practical way to use external libraries in a distributed app. Basically
> it is a way to utilize external code libraries without setting a reference
> to them.

Tony Toews has some introductory material on Late Binding at
http://www.granite.ab.ca/access/latebinding.htm

--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)

Thank you Douglas (and Rick) for that information. Tony's material on late
binding was VERY helpful! I'm not doing anything really esoteric... just
using DAO and some basic Outlook automation (create appointment, create
contact, etc.), so late binding is probably the way to go.

Btw, while searching the late/early binding topic, I stumbled upona VERY
helpful article on VBA error handling by Allen Browne that will also be
useful in my application. I mention it here because Allen's error logging
routine will help me track down errors (including those related to library
bindings) much easier.

http://www.allenbrowne.com/ser-23a.html

Thanks, again, for the pointers!

Regards, Chris

"Douglas J. Steele" wrote:

> "Rick Brandt" <(E-Mail Removed)> wrote in message
> news:8nYjk.13778$(E-Mail Removed)...
> > Chris O''''Neill wrote:
> >>
> >> This brings up another question... If the user has Access/Outlook
> >> 2003 or 2007 installed, is it possible to programmatically search for
> >> msoutl.olb on their system, change the reference to point at that
> >> library, and have the application run properly? Or, will my
> >> application *only* run on an Access/Outlook XP (2002) system? (Btw,
> >> I'm assuming that my application will *not* run on anything earlier
> >> than Access/Outlook XP, right?)
> >>
> >> If the answer to that last question is that it will run so long as the
> >> reference is changed, can someone explain how to programmatically
> >> change the reference? I'm assuming that'd be a DAO routine, right?
> >
> > Search these groups for "Late Binding". It accomplishes exaclty what you
> > are describing although not in the manner you describe. It is the only
> > practical way to use external libraries in a distributed app. Basically
> > it is a way to utilize external code libraries without setting a reference
> > to them.
>
> Tony Toews has some introductory material on Late Binding at
> http://www.granite.ab.ca/access/latebinding.htm
>
> --
> Doug Steele, Microsoft Access MVP
> http://I.Am/DougSteele
> (no e-mails, please!)
>
>
>
>

I spent this evening converting a couple of my Outlook routines to use late
binding. That is REALLY cool!!!! I do hope Dr. Koops is still reading this
thread because even though it doesn't resolve his original problem (i.e. you
still can't bind to an object library that just isn't there) it sure does
make it simpler to deal with multiple versions of a library that is there!

Anyway, I have one more little question regarding the subject of early/late
binding...

In Access 2002/XP, the ADO library is the default and I had to manually
create a reference to the DAO library. I'm assuming I can use late binding
with the DAO library as well, right? If that's the case, then the only
libraries I really need an explicit reference to are the required ones:
Access, VBA, OLE and ADO. Right?

Thanks, again, for all the help! I'm learning SO much! And, someday, I
might actually get this application finished!

Regards, Chris

"Douglas J. Steele" wrote:

> "Rick Brandt" <(E-Mail Removed)> wrote in message
> news:8nYjk.13778$(E-Mail Removed)...
> > Chris O''''Neill wrote:
> >>
> >> This brings up another question... If the user has Access/Outlook
> >> 2003 or 2007 installed, is it possible to programmatically search for
> >> msoutl.olb on their system, change the reference to point at that
> >> library, and have the application run properly? Or, will my
> >> application *only* run on an Access/Outlook XP (2002) system? (Btw,
> >> I'm assuming that my application will *not* run on anything earlier
> >> than Access/Outlook XP, right?)
> >>
> >> If the answer to that last question is that it will run so long as the
> >> reference is changed, can someone explain how to programmatically
> >> change the reference? I'm assuming that'd be a DAO routine, right?
> >
> > Search these groups for "Late Binding". It accomplishes exaclty what you
> > are describing although not in the manner you describe. It is the only
> > practical way to use external libraries in a distributed app. Basically
> > it is a way to utilize external code libraries without setting a reference
> > to them.
>
> Tony Toews has some introductory material on Late Binding at
> http://www.granite.ab.ca/access/latebinding.htm
>
> --
> Doug Steele, Microsoft Access MVP
> http://I.Am/DougSteele
> (no e-mails, please!)
>
>
>
>

While I believe it's possible to use late binding with DAO, realistically I
think it should be added as a reference. It was a stupid decision on the
part of Microsoft not to include it by default in Access 2000 and 2002: they
corrected the error in Access 2003 (and, of course, it's in Access 2007 by
default as well)

--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)


"Chris O''''Neill" <(E-Mail Removed)> wrote in message
news:1B316A0F-565E-464C-ABAC-(E-Mail Removed)...
> In Access 2002/XP, the ADO library is the default and I had to manually
> create a reference to the DAO library. I'm assuming I can use late
> binding
> with the DAO library as well, right? If that's the case, then the only
> libraries I really need an explicit reference to are the required ones:
> Access, VBA, OLE and ADO. Right?

I'm trying to make my application as "idiot proof" as possible because,
frankly, the target audience of my application is computer illiterates.
(Don't tell them I said that! <grin!>)

Is there *any* scenario where the DAO library is *not* going to be on the
end user's computer, or some other problem where my application will totally
blow-up if I early bind to DAO? Or, is it fairly "safe" to just go ahead and
early bind to it? I just want to be sure that there's as few
install/operating problems as possible for my users.

Thanks, again, for all the patience and help!

Regards, Chris

"Douglas J. Steele" wrote:

> While I believe it's possible to use late binding with DAO, realistically I
> think it should be added as a reference. It was a stupid decision on the
> part of Microsoft not to include it by default in Access 2000 and 2002: they
> corrected the error in Access 2003 (and, of course, it's in Access 2007 by
> default as well)
>
> --
> Doug Steele, Microsoft Access MVP
> http://I.Am/DougSteele
> (no e-mails, please!)
>
>
> "Chris O''''Neill" <(E-Mail Removed)> wrote in message
> news:1B316A0F-565E-464C-ABAC-(E-Mail Removed)...
> > In Access 2002/XP, the ADO library is the default and I had to manually
> > create a reference to the DAO library. I'm assuming I can use late
> > binding
> > with the DAO library as well, right? If that's the case, then the only
> > libraries I really need an explicit reference to are the required ones:
> > Access, VBA, OLE and ADO. Right?
>
>
>

There's definitely no way that DAO won't be on the computer. I suppose it's
possible that you could run into a versioning problem. I know that used to
happen in Access 97 (going from DAO 3.50 to DAO 3.51), but I don't believe
it's an issue in newer versions.


--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)


"Chris O''''Neill" <(E-Mail Removed)> wrote in message
news:697052DB-0C8F-44A8-8938-(E-Mail Removed)...
> I'm trying to make my application as "idiot proof" as possible because,
> frankly, the target audience of my application is computer illiterates.
> (Don't tell them I said that! <grin!>)
>
> Is there *any* scenario where the DAO library is *not* going to be on the
> end user's computer, or some other problem where my application will
> totally
> blow-up if I early bind to DAO? Or, is it fairly "safe" to just go ahead
> and
> early bind to it? I just want to be sure that there's as few
> install/operating problems as possible for my users.
>
> Thanks, again, for all the patience and help!
>
> Regards, Chris
>
> "Douglas J. Steele" wrote:
>
>> While I believe it's possible to use late binding with DAO, realistically
>> I
>> think it should be added as a reference. It was a stupid decision on the
>> part of Microsoft not to include it by default in Access 2000 and 2002:
>> they
>> corrected the error in Access 2003 (and, of course, it's in Access 2007
>> by
>> default as well)
>>
>> --
>> Doug Steele, Microsoft Access MVP
>> http://I.Am/DougSteele
>> (no e-mails, please!)
>>
>>
>> "Chris O''''Neill" <(E-Mail Removed)> wrote in
>> message
>> news:1B316A0F-565E-464C-ABAC-(E-Mail Removed)...
>> > In Access 2002/XP, the ADO library is the default and I had to manually
>> > create a reference to the DAO library. I'm assuming I can use late
>> > binding
>> > with the DAO library as well, right? If that's the case, then the only
>> > libraries I really need an explicit reference to are the required ones:
>> > Access, VBA, OLE and ADO. Right?
>>
>>
>>