Error 48 in Access 2000 using Outlook

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have an Access 2000 application that needs to use Outlook to send messages.
I have included the MSOUTL.OLB in my setup distribution and it is placed in
the System32 directory of windows. When I run the .mde file and attempt to
use the Outlook to send a mail message I get: Error in Loading DLL, Runtime
error 48. Any assistance would be greatly appreciated.

The VB code looks like:
Dim objOLApp As Outlook.Application
Dim myItem As Variant
Dim Subject As String, Message As String, GenericAcct As String

Subject = "Mysubject"
Message = "Mymessage"

Set objOLApp = New Outlook.Application
Set myItem = objOLApp.CreateItem(olMailItem)
myItem.SentOnBehalfOfName = GenericAcct
myItem.To = EmailTo
myItem.Subject = Subject
myItem.Body = Message
myItem.Send
 
The MSOUTL.OLB file isn't redistributable... the end user must have a
version of Outlook on their machine. The error is most likely coming from
dependencies from MSOUTL.OLB (i.e. other files/dlls etc it depends on) not
being present. The fix is to require that your enduser install Outlook or
provide some other method to send email (like a 3rd party library - I use
the Codestone library from www.codestone.co.uk in Access and VB and have no
troubles).
 
Scott,
These machines do have Outlook on them, so I took out the .olb out of the
installation, so it is just referencing the released .olb but am having the
same result. Any thoughts. Unfortunately, I must use MS Outlook as that is
the corporate email system.

Regards,
Jeff
 
Did your installation originally install and register the msoutl.olb you
included? If so, you may have broken the exisiting version of Outlook. To
test this, you could install your new install routine on a machine that you
haven't installed the old routine on and try it from there. If it works,
then you'll probably have to reinstall outlook on the problem machines. You
could ___try___ locating the msoutl.olb library on the offending machine and
re-registering it ... if no other libraries were altered, you may get lucky.
 
Back
Top