Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Make database available on the internet

Status
Not open for further replies.

Tessadear

Technical User
Mar 7, 2006
26
BB
I need to make my database available on the net so that users can input data in forms already created in access.

Right now I can change the object name in the database to html and upload objects to my website but then the data is only read only. On some of my forms I need to have the users input information. Can anyone lead me to a link which explains what I need to do.
 
What you are doing is creating STATIC web pages.
There are a couple of ways to have remote users access your database. Basically directly or indirectly.
One way is to create a data access page (DAP). But forget what you know about how an access form transfers data to another form or query. With Data Access Pages (DAP), you're creating WEB PAGES. Thus to transfer data from a page to another you need to write cookies. The language you'll be using will be VBScript or JavaScript. Remember, you're coding in the Internet Explorer environment, NOT ACCESS. Also, I've found most IT departments aren't familiar with the XML produced by DAP's. So they'll tell you to rewrite it in ASP or something. DAP's been around for about 6 years, yet few IT people have learned it. There are other pain in the neck nuances about coding Access for the web - it's a loooong learning curve.
Put up a Citrix server ( Then your clients can just login remotely and your Access database can just be stand alone.
If you don't like the Citrix server idea, I would say you could learn SQL or MySql quickly (relatively speaking) and use it to access your Access.
If you're on an INTRAnet, you could split your database (open the database. Keep all tables, forms, queries, etc. closed. Click Tools - Database Utilities - Database Splitter). This creates two files - one with just the tables (Backend), the other with queries, forms, macros, etc. (Frontend). They will be linked. You would place the BE on the server. You would then make a replica of your FE (Tools - Replication - Create Replica). You would do this as many times as needed (one for each user). The replicas would then go on each individual client. They then have access to the same data (the tables on the server), but they can do their own individual work (creating forms, queries, etc.). Then once a week or whatever, you can sync the different FE's (Tools -Replication - Synchronize Now). That's a very quick review. It's in any good Access book. It's actually pretty straight forward, and quick to set up.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top