Calling Access Macro via .asp

[paulmitchell507]

I would like to call a macro in Access 2000 via a asp file. I access
the DB via ADO. I realise that I would need to place the database on
the server, but that's not a problem as its a intranet site.

 

[Norman Yuan]

Even you can place it on the server, it is really bad idea: if the Macro is
just used for manipulate data without MS Access application itself, then you
can do it all in ASP code. If the Macro does something involving MS Acccess
user interface, then, automating application such as MS Access on the server
will crash your ASP web application in many ways sooner or later.

 

[paulmitchell507]

Even you can place it on the server, it is really bad idea: if the Macro is
just used for manipulate data without MS Access application itself, then you
can do it all in ASP code. If the Macro does something involving MS Acccess
user interface, then, automating application such as MS Access on the server
will crash your ASP web application in many ways sooner or later.






- Show quoted text -

The reason I wanted to call a Access Macro was because I want to run a
module of code. The code does not involve the MS Access user
interface. Are you saying that anything that I currently accomplish
via a Access module I can also do in ASP?

 

[Norman Yuan]

If your macro just manupulate data, of course you can do it with ADO/DAO. In
this case, you DO NOT need MS Access installed on the server. I saw your
later post in the regard of automating MS Access to send email after the
macro is done, via Outlook (ouch, automating MS Access and then MS Access
automating Outlook on a web server, even it is a intranet one? it is crazy
idea, to say the least). I am completely against the way you do it and am
sure your applicatin will not run smoothly as you expected, even you can
manage it to work in your a few tests. But as for the reason of failed
SendTo, you need to configure IIS to run your application with a user
account that has permission to run Outlook with given Outlook profile.

Come on, man, if you already have the required data process done in MS
Access macro, why you need a server side ASP app, which runs MS Access? If
you want to take advantage of serverapplication, then leave MS Access alone,
write your data process code with ADO/DAO, and do your email thing with
server side manner.

Even you can place it on the server, it is really bad idea: if the Macro
is
just used for manipulate data without MS Access application itself, then
you
can do it all in ASP code. If the Macro does something involving MS
Acccess
user interface, then, automating application such as MS Access on the
server
will crash your ASP web application in many ways sooner or later.






- Show quoted text -

The reason I wanted to call a Access Macro was because I want to run a
module of code. The code does not involve the MS Access user
interface. Are you saying that anything that I currently accomplish
via a Access module I can also do in ASP?

 

[paulmitchell507]

If your macro just manupulate data, of course you can do it with ADO/DAO.In
this case, you DO NOT need MS Access installed on the server. I saw your
later post in the regard of automating MS Access to send email after the
macro is done, via Outlook (ouch, automating MS Access and then MS Access
automating Outlook on a web server, even it is a intranet one? it is crazy
idea, to say the least). I am completely against the way you do it and am
sure your applicatin will not run smoothly as you expected, even you can
manage it to work in your a few tests. But as for the reason of failed
SendTo, you need to configure IIS to run your application with a user
account that has permission to run Outlook with given Outlook profile.

Come on, man, if you already have the required data process done in MS
Access macro, why you need a server side ASP app, which runs MS Access? If
you want to take advantage of serverapplication, then leave MS Access alone,
write your data process code with ADO/DAO, and do your email thing with
server side manner.






The reason I wanted to call a Access Macro was because I want to run a
module of code.  The code does not involve the MS Access user
interface.  Are you saying that anything that I currently accomplish
via a Access module I can also do in ASP?- Hide quoted text -

- Show quoted text -

Dear Norman, thank you for your advice so far!
Until now, I have been working with Access 2000. I have been tasked
with creating a company holiday request database. My original plan
was to post a Data Access Page on the company intranet, linked to the
access database. That was until I discovered that you can only enter
data via a DAP if you have internet explorer. I need a solution that
will work with any browser.

The data manupulation that I run in access is dependent on the data
entered via the browser, this is why i was attempting to write a small
ASP app that would enter data into the database and then run a access
macro.

It looks as if I will have to learn how to write the data code with
ADO.

Regards,
Paul

 

[Norman Yuan]

To build a web interface of intranet app, ASP is fairly easy and it wouldn't
be a problem to use Jet database (*.mdb) as data source. You use ADO to
access/update data from/to the database file. Do not automate MS Access from
web server. With web app, ASP is bit old technology (though still OK for
small project), but Data Access Page is dead already. But if you haven't
learned much on web app or ASP, you may want to skip it and go to ASP.NET
(you can download free Visual Studio Web Develop Express from MS to get
started), which not only can get you easily build the web app for holiday
requesting/approving, it will also make the sending email from server (the
web app) a lot easier (not automating Outlook on the server).

If your macro just manupulate data, of course you can do it with ADO/DAO.
In
this case, you DO NOT need MS Access installed on the server. I saw your
later post in the regard of automating MS Access to send email after the
macro is done, via Outlook (ouch, automating MS Access and then MS Access
automating Outlook on a web server, even it is a intranet one? it is crazy
idea, to say the least). I am completely against the way you do it and am
sure your applicatin will not run smoothly as you expected, even you can
manage it to work in your a few tests. But as for the reason of failed
SendTo, you need to configure IIS to run your application with a user
account that has permission to run Outlook with given Outlook profile.

Come on, man, if you already have the required data process done in MS
Access macro, why you need a server side ASP app, which runs MS Access? If
you want to take advantage of serverapplication, then leave MS Access
alone,
write your data process code with ADO/DAO, and do your email thing with
server side manner.






The reason I wanted to call a Access Macro was because I want to run a
module of code. The code does not involve the MS Access user
interface. Are you saying that anything that I currently accomplish
via a Access module I can also do in ASP?- Hide quoted text -

- Show quoted text -

Dear Norman, thank you for your advice so far!
Until now, I have been working with Access 2000. I have been tasked
with creating a company holiday request database. My original plan
was to post a Data Access Page on the company intranet, linked to the
access database. That was until I discovered that you can only enter
data via a DAP if you have internet explorer. I need a solution that
will work with any browser.

The data manupulation that I run in access is dependent on the data
entered via the browser, this is why i was attempting to write a small
ASP app that would enter data into the database and then run a access
macro.

It looks as if I will have to learn how to write the data code with
ADO.

Regards,
Paul