Access 2000 Find Inbox at Runtime

[Bob Dydd]

Hi Everybody

I have an Access 2000 MDB with the Usual FrontEnd/BackEnd Arrangement.
The program depends on being able link to "Inbox" in Ms Outlook 2000.

This is easy enough to do from the FrontEnd and has been OK while me
and the missus have been using the program ourselves.

Now We want to be able to give the program to others who mainly do
not have MS Access installed., or if they do, have no idea what it is
about

To make matters worse some are using different versions of MS Outlook
MS Outlook 2003 50%
MS Outlook 2002 25%
MS Outlook 2000 25%

The program has to be supplied as a runtime so something that operates
from a form would be ideal.

It would need to check if any version of Ms Outlook is present
determine which one and then link to it.

This has taxed my brain for more than a few hours, and I wondered if
anyone else had any ideas.

Regards Smiley Bob

[Sue Mosher [MVP-Outlook]]

The easiest way to test whether Outlook is present is to see what
CreateObject("Outlook.Application") returns.

The article at
http://msdn.microsoft.com/library/en...olexcoutlk.asp may be
at least close to what you're looking for, in terms of database linking
code.

--
Sue Mosher, Outlook MVP
Author of
Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers
http://www.outlookcode.com/jumpstart.aspx
"Bob Dydd" <sm*******@hotmail.com> wrote in message
news:a6********************************@4ax.com...

Hi Everybody

I have an Access 2000 MDB with the Usual FrontEnd/BackEnd Arrangement.
The program depends on being able link to "Inbox" in Ms Outlook 2000.

This is easy enough to do from the FrontEnd and has been OK while me
and the missus have been using the program ourselves.

Now We want to be able to give the program to others who mainly do
not have MS Access installed., or if they do, have no idea what it is
about

To make matters worse some are using different versions of MS Outlook
MS Outlook 2003 50%
MS Outlook 2002 25%
MS Outlook 2000 25%

The program has to be supplied as a runtime so something that operates
from a form would be ideal.

It would need to check if any version of Ms Outlook is present
determine which one and then link to it.

This has taxed my brain for more than a few hours, and I wondered if
anyone else had any ideas.

Regards Smiley Bob

[DL]

You will need Access Developers addition, in order to distribute as a
runtime. Your installation installer would also need to determine version of
MDAC installed on the sys, in order to asertain whether another version
should be installed

"Bob Dydd" <sm*******@hotmail.com> wrote in message
news:a6********************************@4ax.com...

Hi Everybody

I have an Access 2000 MDB with the Usual FrontEnd/BackEnd Arrangement.
The program depends on being able link to "Inbox" in Ms Outlook 2000.

This is easy enough to do from the FrontEnd and has been OK while me
and the missus have been using the program ourselves.

Now We want to be able to give the program to others who mainly do
not have MS Access installed., or if they do, have no idea what it is
about

To make matters worse some are using different versions of MS Outlook
MS Outlook 2003 50%
MS Outlook 2002 25%
MS Outlook 2000 25%

The program has to be supplied as a runtime so something that operates
from a form would be ideal.

It would need to check if any version of Ms Outlook is present
determine which one and then link to it.

This has taxed my brain for more than a few hours, and I wondered if
anyone else had any ideas.

Regards Smiley Bob

[Tony Toews]

Bob Dydd <sm*******@hotmail.com> wrote:

I have an Access 2000 MDB with the Usual FrontEnd/BackEnd Arrangement.
The program depends on being able link to "Inbox" in Ms Outlook 2000.

This is easy enough to do from the FrontEnd and has been OK while me
and the missus have been using the program ourselves.

Now We want to be able to give the program to others who mainly do
not have MS Access installed., or if they do, have no idea what it is
about
For those without the runtime you need to use the MOD to create a runtime. Trouble
is it has problems when distributed to sites running different versions of software
and may no longer be available for A2000.

Microsoft Access (Office) Developer Edition FAQ
http://www.granite.ab.ca/access/developereditionfaq.htm
To make matters worse some are using different versions of MS Outlook
MS Outlook 2003 50%
MS Outlook 2002 25%
MS Outlook 2000 25%

Late binding means you can safely remove the reference and only have an error when
the app executes lines of code in question. Rather than erroring out while starting
up the app and not allowing the users in the app at all. Or when hitting a mid, left
or trim function call.

You'll want to install the reference if you are programming or debugging and want to
use the object intellisense while in the VBA editor. Then,. once your app is
running smoothly, remove the reference and setup the late binding statements.

Sample code:
' Declare an object variable to hold the object
' reference. Dim as Object causes late binding.
Dim objWordDoc As Object
Set objWordDoc = CreateObject(" Word.Document")

For more information including additional text and some detailed links see the "Late
Binding in Microsoft Access" page at http://www.granite.ab.ca/access/latebinding.htm

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm

[Bob Dydd]

On Fri, 30 Jul 2004 19:01:03 GMT, Tony Toews <tt****@telusplanet.net>
wrote:

Hi All

Thanks to everyone that answered

We have the Access 2000 developers edition and have distributed a few
with the "Package and Deployment manager (PDM). but most users are
having difficulty with relinking the backend AND finding and Linking
the Inbox.

I am using a linking form that I bought from Database Creations. THis
has all the code in the code behind forms to refresh links and is able
to cope with more that one back end. .... The difficulty is that it
"sees" the inbox as a table that it cannot link to and produces an
error. So I am a bit stuck there as well.

If anyone has any pointers I would be most grateful.

The PDM that is supplied with ODE is NOT a great piece of Kit. IMHO.
Barely adequate. So before further redistribution this will have to be
replaced.

Reading through the groups, the bulk of opinion seem to be to use
Installshield in conjuction with Sage Scripts, but I have yet to try
this out. About $900 to find the answer to that one, Whew!!

Bob Dydd <sm*******@hotmail.com> wrote:

I have an Access 2000 MDB with the Usual FrontEnd/BackEnd Arrangement.
The program depends on being able link to "Inbox" in Ms Outlook 2000.

This is easy enough to do from the FrontEnd and has been OK while me
and the missus have been using the program ourselves.

Now We want to be able to give the program to others who mainly do
not have MS Access installed., or if they do, have no idea what it is
about

For those without the runtime you need to use the MOD to create a runtime. Trouble
is it has problems when distributed to sites running different versions of software
and may no longer be available for A2000.

Microsoft Access (Office) Developer Edition FAQ
http://www.granite.ab.ca/access/developereditionfaq.htm

To make matters worse some are using different versions of MS Outlook
MS Outlook 2003 50%
MS Outlook 2002 25%
MS Outlook 2000 25%

Late binding means you can safely remove the reference and only have an error when
the app executes lines of code in question. Rather than erroring out while starting
up the app and not allowing the users in the app at all. Or when hitting a mid, left
or trim function call.

You'll want to install the reference if you are programming or debugging and want to
use the object intellisense while in the VBA editor. Then,. once your app is
running smoothly, remove the reference and setup the late binding statements.

Sample code:
' Declare an object variable to hold the object
' reference. Dim as Object causes late binding.
Dim objWordDoc As Object
Set objWordDoc = CreateObject(" Word.Document")

For more information including additional text and some detailed links see the "Late
Binding in Microsoft Access" page at http://www.granite.ab.ca/access/latebinding.htm

Tony

[Tony Toews]

Bob Dydd <sm*******@hotmail.com> wrote:

We have the Access 2000 developers edition and have distributed a few
with the "Package and Deployment manager (PDM). but most users are
having difficulty with relinking the backend AND finding and Linking
the Inbox.

I am using a linking form that I bought from Database Creations. THis
has all the code in the code behind forms to refresh links and is able
to cope with more that one back end. .... The difficulty is that it
"sees" the inbox as a table that it cannot link to and produces an
error. So I am a bit stuck there as well.

If anyone has any pointers I would be most grateful.
I've never linked to the Inbox in Outlook from Access. Hopefully others have.
The PDM that is supplied with ODE is NOT a great piece of Kit. IMHO.
Barely adequate. So before further redistribution this will have to be
replaced.

Reading through the groups, the bulk of opinion seem to be to use
Installshield in conjuction with Sage Scripts, but I have yet to try
this out. About $900 to find the answer to that one, Whew!!

Yup, SageKey seems to be the best alternative mentioned in the newsgroups.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm