web based database

[tizwaz]

I want to make a simple database in which staff can log complaints and place it on our staff intranet. However I don't know how to adapt a standard database for web use. Can anyone advise me?

 

[fneily]

Since it's on an INTRAnet, you have a few choices.
You can place the database on a shared drive so everyone has access to it.
You can create what's known as Front End/Back Ends for it.
If you dare, you can create Data Access Pages (DAP's, which are web pages) for their input.
You can create web pages in ASP.

 

[tizwaz]

I'm ok creating a database which could be saved to the shared drive and I know how to do a front and back end. However data access pages etc are new to me. I think it would be more accessible if the data entry form was on the intranet but don't know how to go about it. I've just had a go at creating a simple form and am already having difficulties. For eg the table set the default date to DATE() but this doesn't work in the form. I would want a dependant combo box eg 1st box pick location, 2nd box pick room dependant on the location you picked. I've done this in normal forms before using a query which refers to the form control but can't see how this would work in the data access form. Also do you have to click the save button in order to save the record as I think many people would just close the web page once they have entered the record. If I can resolve these things it might work - is it a simple task for our web developer to post on the data access page or would it require more work from him? Finally what is ASP?

 

[fneily]

ASP stands for Active Server Page and is use to create interactive web pages. If you search through this forum, and the other Access forums, you'll find discussions that suggest to use ASP over DAP's. There's even an Asp forum - Microsoft: Active Server Pages (ASP).
I noticed in your post you refer to DAP's as forms. Concept - Dap's are NOT forms. They are web pages that reside outside of Access. You DO NOT code them with VBA. You are coding in the Internet Explorer environment and thus use either JScript or VBScript. So forget what you know about forms.
If you do a search on "data access page" and DAP in this forum, you'll find quite a few questions/answers on DAP's.
Some sites for reading:
How to Create a Data Access Page to Open to New Records Only

http://support.microsoft.com/?kbid=262453

How to deploy data access pages over the Internet

http://support.microsoft.com/?kbid=264080

How to Find a Record from a Drop-down List in a Data Access Page

http://support.microsoft.com/?kbid=247823

How to use VBScript to Synchronize Two Data Access Pages

http://support.microsoft.com/?kbid=233487

Be prepared to spend alot of time of your project.

 

[PaulBricker]

tizwaz, I would suggest staying away from Data Access Pages. HTML is the best and easiest way to get this done. The process is something like this. You create an HTML form to collect your data. You have a submit button on the HTML page that when you click it, calls an ASP (Active Server Page) page. This ASP page is essentially ADO code that takes the information from the HTML page and submits it to the database (or the reverse if you are pulling info from the database to your HTML page). If you are familiar with MS Access, then most of the coding is fairly straight forward. What you will need to get a better handle on is the HTML and ASP. Neither is rocket science. YOu can have a look at these to Tek-Tips forums

The HTML forum
forum215

and the ASP forum
forum333

Most of the questions you have should be directed to these forums but try googling for things like the HTML form and simple ASP pages. There is a lot of information out there that will give you a place to start. Then talk with your web developer. You should be able to get something like this up and running without much trouble.

Paul

 

[fneily]

tizwaz - as you can see, and you'll find in other posts if you do a search, there'll be a debate between using DAP's or ASP. I disagree with PaulBricker. Noticed he said that "HTML is the best and easiest way to get this done." DAP's are html and XML. And he is correct in saying that ASP is an intermediate - that you must create. DAP's place data directly into, and take directly from, your tables/queries.
I like these two statements of his:
"What you will need to get a better handle on is the HTML and ASP."
"You should be able to get something like this up and running without much trouble"
On one hand you need time to learn HTML and ASP. But, on the other hand, it won't take you long. ???????
Which ever you choose, it'll take time.

 

[PaulBricker]

I'm sure it seemed I was rebutting fneily's proposal to use the DAP's for your pages, but I was not. I had not seen that proposal before submitting my recommendations. I recommend using the HTML and ASP mainly because DAP's present a lot of limitations that HTML and ASP don't. One, you can not view DAP pages from any browers except IE. Also, learning HTML and ASP is not difficult and gives you a great deal of flexibility that you will not have with the DAP's.
Got a meeting, got to go.

Paul

 

[tizwaz]

thanks v much - I'll see what I can do