MS Access & Web Deployment

[Zwoker]

Hi All,

I'm trying to find out what is possible in the way of web deployment (the Access help doesn't seem to tell me enough) in MS Access 2003.

I have a make table query, and a quite complicated report that prints the table details.

I have played with the Pages feature in MS Access to make a web page that happily sits on my web server and shows the table records one at a time, but what I want is more complicated than that.

My ideal solution would be a form that sits on the web server that allows the required user parameters to be entered (lets assume they are a date and a product code). The user enters the parameters they want in their web browser, clicks the "go" button on the form. That then triggers MS Access to run the query using the user-entered parameters and then runs the report, and shows the results to the user, where they have the option of printing the report.

Is that possible with standard MS Access? I tried out the Forms option, but it didn't seem to convert it to a web page in any meaningful way. It just seems to create a static html page.


Thanks for any feedback or suggestions.

[lee123]

you probably need a microsoft developer

[MMcCarthy]

You need to design your form in the web language you are currently using such as php and link the access table to it. You would probably do this through a DSN connection. I'm afraid I can't give more technical details than that but you can post a question in the relevant web development forum and they should be able to help you.

[wideasleep]

I have been looking at programs such as Microsoft Expression Web and FLEX 2 by Adobe. I like FLEX 2 but it seems to have a steeper learning curve where Expression Web seems more user friendly.

[Zwoker]

Hi,

Thanks for the feedback.

I had been hoping that there was a simple utility built into MS Access that would do what I wanted.

I have discovered that I can save my report as a "Data Access Page" which initially looked good until I saw that the web page wasn't executing the VBA code I had put into the report. Other than that it looked quite nice.

I think, as suggested, I'll investigate non-Access solutions and see how they go.