Access 2000 asp

[paulmitchell507]

I have the following code in a asp file on my server 2003 IIS server.
The code works fine, it open the databse and runs the macro. However,
if I change the staff list macro so it uses the SendTo function, the
code will not send an e-mail. I can log onto the server and run the
macro from access no problem. The error message I receive when
running the asp code is

MSAccess error '800a08f5'

Microsoft Access can't send a message for the reason stated in the
preceding alert.

There is no preceding alert, I have outlook 2000 installed and open on
the server, I am unable to find many references to 800a08f5'

Regards,
Paul
<%

Dim objAccessReport

Set objAccessReport = Server.CreateObject("Access.Application")
objAccessReport.Visible = False
objAccessReport.OpenCurrentDataBase "c:\Inetpub\test_intranet
\staff.mdb"
macroname = "staff list"
objAccessReport.DoCmd.RunMacro macroname
objAccessReport.CloseCurrentDatabase
Set objAccessReport = Nothing
Response.Write "Your macro has been run!"

%

 

[paulmitchell507]

Access isn't designed to be run on a web server as a web app or from a web
page.  The reason is because Access, like all the office apps, is designed
for user interaction (try pushing the "ok" button on an Access msgbox from a
web app), and if the user interaction isn't done correctly, the web server
can hang.  Not just that web app, but the whole web server.

Write the app in asp to send the email.

Chris
Microsoft MVP

Thank you for your reply
I guess I was just trying to save research time!
I will just have to learn how to write the app in asp.

 

[Bill Mosca]

Paul

A bet the "preceding alert" is that annoying warning that "a program is
trying to send an email. Do you want to allow it?"

Because no one is there to click the Yes button, it times out. There are a
few workarounds, one being to turn off the warning at the Exchange server,
but that might be too extreme. Another popular solution is Outlook
Redemption at www.dimastr.com/redemption/