Run a form through a webpage

[IANGRAND]

Does anyone have the HTML code to embedd/run an access form through a webpage?

cheers

Ian

 

[PHV]

In the access help take a look at Data Access Page (DAP)

Hope This Helps, PH.
Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884 or FAQ181-2886

 

[BNPMike]

Data Access Pages rely on certain Microsoft components being installed on the client so for example they wouldn't work on my work pc until someone came and installed the extra bits.

 

[FancyPrairie]

BNPMike is correct. DAP require that the Office Web Components are installed on the user's machine. DAP created using the Office 2000 web components required a license. However, DAP created using the Office XP web components don't require a license (unless you've incorporated the spreadsheet control or pivot chart and you want the user to be able to edit the data with these controls). Note that if you create a DAP using Access 2003, it uses the Office XP web components, not the Office 2003 web components.

Also note that included with the code that Access 2003 generates for DAP is code that checks to see if the office web components exist on the user's machine. If not, it downloads and installs them. However, it's been rough battle getting it all to work. First, Access 2003 uses the Office XP web components (owc10.dll), but attempts to install the Office 2003 web components (owc11.dll). If office 2003 standard edition is installed on the user's machine, they don't recieve owc10.dll. However, if Access 2003 is installed then, in addition to receiving owc11.dll, they also get owc10.dll. I didn't know this at the time, so it was very frustrating at the beginning. All my users had Office 2003 installed and some users had no problem running my web pages (because they happened to have owc10.dll installed), others did have problems (did not have owc10.dll installed). In addition, internet/intranet security had to be setup correctly on the user's machine (I ended up setting up a trusted site.)

I've created a couple of DAP (Access 2000 and 2003) and did my best to make them work. I hoped to sell the concept with other programmers in our company. I liked the concept of client-side scripting. You don't have to call another page to validate data. Plus a lot of other advantages. However, I'm abandoning them now. Mainly because of Microsoft's editor. It's very unstable and extremely slow. I've had a lot of problems with the package. I'm switching to ASP.Net and VB.Net using VisualStudio. We'll see how that goes.

I guess I rambled on. I meant to add quick comment. But you caught me at a bad time when my frustration level with DAP is high.