Outlook dependency

  • Thread starter Thread starter John Cosmas
  • Start date Start date
J

John Cosmas

I have Outlook functionality built into my Access application and I would
like to ship with my installation the libraries, files, OLB's and other
necessary files required to get the application to work in runtime mode on
the target client. If anyone knows how to locate, find, or has references
to file lists at msdn or elsewhere the filelist I will need to make this
happen, please let me know.

TIA
John Cosmas
 
John,

Copying and deploying to another user any of the component files of Outlook
or any other Office product is a violation of your End User License
Agreement. See:

"Section 2. Description of Other Rights and Limitations

Separation of Component Parts. The Software Product is licensed as a single
product. Its component parts may not be separated for use on more than one
Device unless expressly permitted by this EULA."

In order for Automation of Outlook or any other Office product to work from
within a user's copy of an Access database, the user must also have that
Office product installed.
 
Hi Cheryl
What about outlctl.dll - it comes only with outlook yet you can use it to
put outlook into access or even a web page for that matter - ms even provide
a help file for it. Once you insert it into access which gives you most of
the outlook functionality you can then use it to link to any mapi store

Just thinking out loud!
 
I really do not know enough about the Outlook View Control to make any
comment on it. Are you saying that it can be distributed to and provide
some Outlook functionality to users who do not have Outlook installed?
 
If I understand your first paragraph correctly, you would not need to use
Outlook at all if you could determine a method to parse out a text stream
using only Access VBA.

If you would describe the Text Stream ... where it comes from and how it is
formatted. And, describe what you want to do with items in the Text
Stream in your Access application, I am sure we can come up with a solution.
 
Let me refine my request and maybe we can isolate the response a bit. My
code does a createobject method and launches Outlook.Application. I use the
CreateItem method so I can pass a Name and Address stream so I can use the
Outlook function to parse out the appropriate properties out - FirstName,
LastName, ...AddressStreet, ...AddressPostalCode items without having to
write code. I cannot find parsing code that will do this from scratch, or
otherwise I would not have to instantiate Outlook application/function in my
code. Let me know if we're heading in the right direction, or make
suggestions as to how I'd have to parse out the individual pieces without
the Outlook function.

Cheryl - I clearly understand the licensing issues, but most of our clients
have a full blown install of Office. I'm using the runtime so I can support
demo installations. We have to showcase our application on some clients who
have older versions of Office and after they've bought into our app, they'll
usually sign over the desktop maintenance and so we usually upgrade the
whole machine up to par.

TIA
John Cosmas
 
I am using the ContactItem function and filling in the FullName and
BusinessAddress property. After which, it will process/parse the text and
return to me the following items as I use the get method/technique -
FirstName, LastName, MiddleName, Title, Suffix, BusinessAddressStreet,
BusinessAddressCity, BusinessAddressPostalCode,
BusinessAddressPostOfficeBox, BusinessAddressState, etc. This method in
Outlook seems very reliable and so I went as far as writing code to parse
the name portions and splitting the address into multiple lines (because up
to 4 lines of an address can be passed/supplied). Besides, there are other
future functions employing the OUTLLIB.DLL that I will want to leverage
(import, export, translation, XML). Some of our customers also do not
install Outlook with their Office package, because they are asked to use
Notes, Eudora, Time & Chaos, etc...
 
No! I used Outlook's ContactItem function has the features I need
specifically to handle the parsing of the Name and Address text streams.
This cannot be found in MAPI, although we'll use CDONTs for messaging, which
we've been able to do without a problem. The problem still remains that I
need to employ ContactItem features to parse the contact information.
Thanks for the input.
 
John Cosmas said:
I have Outlook functionality built into my Access application and I would
like to ship with my installation the libraries, files, OLB's and other
necessary files required to get the application to work in runtime mode on
the target client. If anyone knows how to locate, find, or has references
to file lists at msdn or elsewhere the filelist I will need to make this
happen, please let me know.
Click to expand...

Given that Outlook may or may not exist on the target system, and you
don't know what version it will be I'd suggest using Late Binding.

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
 
Tony;

I did use the late binding technique and it does work without including the
reference. My problem through still remains, because the client may not
have Outlook installed at all. Unfortunately, I can't simply ship the
Outlook OLB file, because that by itself does not work. I suspect that the
full installation of Outlook via the Office Setup installs a bunch of
support items that makes up the functionality. Really, I just need the
support of the Name and Address parsing functions so I can pass the FullName
and BusinessAddress and expect the rest to be retrieved using the get
method, which allows me to fetch the PostalCode, PostOfficeCode, State, City
and other respective parts. If anyone has an idea as to a function that
already does this, please let me know.

John Cosmas
 
John Cosmas said:
I did use the late binding technique and it does work without including the
reference. My problem through still remains, because the client may not
have Outlook installed at all.

Really, I just need the
support of the Name and Address parsing functions so I can pass the FullName
and BusinessAddress and expect the rest to be retrieved using the get
method, which allows me to fetch the PostalCode, PostOfficeCode, State, City
and other respective parts. If anyone has an idea as to a function that
already does this, please let me know.
Click to expand...

Ah, then I'd suggest writing your own parser. You have better control
anyhow.

HOWTO: Parse City, State, and Zip Code into Separate Values
http://support.microsoft.com/?kbid=168798
Now this is for peoples names rather than business names:
HOWTO: Parse a Person's Name into Multiple Variables
http://support.microsoft.com/?kbid=168799

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
 
Back
Top