Accessing MS Access forms via a browser (Access 2000)

Topic

New Reply

Hi All,
I need to access a form (with its vb code functionality) via a browser. Could ASP do this?. Any suggestion of how to go about this?,
Thankyou
Mark

Reply | Quote

Replies

Access forms are not available from a browser, they are peculiar to Access. Data Access Pages are browser pages but they only work on intranets and where all the users have Access on their machines.

I suspect that it would be very difficult to recreate the complex functionality of an Access form in a browser page, but I don’t write ASP, so I could be mistaken. What exactly is it that you are trying to achieve? Do you want to use the browser to capture data for the database, are you trying to use Access to push data to a browser page for display, or what? The more specific you get, the easier it will be for the web-inclined among us to give you some useful answers.

Reply | Quote

Hi Charlotte,
I don’t mind if its Data Access Pages, as it will be based on one machine. All I want is to have a command button on the page in the browser, that once pressed, it executes the command button that is on the access form, thus executing the underlying vb code that is underneath it. Possible?

Reply | Quote

Data Access Pages may be your answer, but you can’t run VBA code from your browser. What you get instead is VBScript (a rather limited subset of VB) that runs under Internet Explorer. DAPs are a bit cleaner with 2002, but you should be able to create one in 2000 and see if you can get it to do what you want.

Reply | Quote

Thanks Wendell,,,hhhhmmm, I guess it looks like l should just stick to using the form in access. I guess if its not broke, why fix it. But I was just aiming for this idea so I can intergrate it with my other asp pages.

Reply | Quote

You can definately construct web forms to work with an access in the backend but don’t expect the full functionality of Access forms in HTML/asp. I do this sort of thing fairly often and find it entertaining enough… But, the question is, why should you use a browser to interface with Access? Then best (perhaps only) reason is to create pages that other people (even yourself, remotely) want to look at and interact with the Access-driven data. If you’re working on an Access db on one machine and for yourself only, don’t bother unless you feel the need to learn how to create data-driven web pages from Access.

But if you want to integrate the Access db with your other asp pages, think in terms of what ‘subsets’ of the Access db you want to expose on a particular page (for example, a company directory listing pulled as a recordset from a table or query) — that way, you don’t need to try to re-create an Access form out of whole cloth on a web page, which is difficult and likely not necessary.

Reply | Quote

Hi Steve,
I see your point, but I was just contemplating the idea for the future, in case there will need to be more then one user who might need to access the database. At this point in time, it might not be a neccessity, but it will eventually become one. I guess for the time being I’ll make the forms look really stunning
Thanks for your info though.
Mark

Reply | Quote