|
Home > Archive > MS Access Multiuser > May 2005 > Excel & Outlook References in Access
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Excel & Outlook References in Access
|
|
| Brian Arnold via AccessMonster.com 2005-04-28, 11:24 am |
| We are slowly moving from Windows '98 to XP but our Excel & Outlook
references continue to be a problem. Most of my load code is based upon
the day (date()) and it can not be found when the XP users go in and
upgrade the references to 10.0 Excel & Outlook. Is there any way I can
"set" the Excel & Outlook references based upon the OS you are going into
the database with? I added the code below, but it doesn't seem to be
enough:
Dim appExcel As Object
Set appExcel = CreateObject("Excel.Application")
Dim appOutLook As Object
Set appOutLook = CreateObject("Outlook.Application")
Any ideas?
Brian
| |
| Douglas J. Steele 2005-04-28, 8:26 pm |
| If you're using that code, you don't need references to be set. Simply
remove them, and your code will work, with one caveat: you cannot use any of
the built-in constants from either application. If you are using built-in
constants, either replace all references with the actual value, or define
global variables of your own to supply the values.
--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)
"Brian Arnold via AccessMonster.com" <forum@nospam.AccessMonster.com> wrote
in message news:23c44b544eb54d2
09bfc2834e18b927e@Ac
cessMonster.com...
> We are slowly moving from Windows '98 to XP but our Excel & Outlook
> references continue to be a problem. Most of my load code is based upon
> the day (date()) and it can not be found when the XP users go in and
> upgrade the references to 10.0 Excel & Outlook. Is there any way I can
> "set" the Excel & Outlook references based upon the OS you are going into
> the database with? I added the code below, but it doesn't seem to be
> enough:
>
> Dim appExcel As Object
> Set appExcel = CreateObject("Excel.Application")
> Dim appOutLook As Object
> Set appOutLook = CreateObject("Outlook.Application")
>
> Any ideas?
> Brian
| |
| Brian Arnold via AccessMonster.com 2005-05-12, 9:25 am |
| Doug,
Thanks for the info, but I continue to have issues with Outlook once the
references have been removed. I'm getting caught up on these lines of code:
Dim ol As Outlook.Application
Set ol = New Outlook.Application
Set NewMessage = ol. CreateItem(olMailIte
m)
..Attachments.Add strPath, olByValue
While I do tell Access when this function is started,
Dim appOutLook As Object
Set appOutLook = CreateObject("Outlook.Application")
It still gets caught up on these lines. Any suggestions?
Thanks again for your help thus far,
Brian
--
Message posted via http://www.webservertalk.com
|
|
|
|
|