Link to Access db from website doesn't work

[Guest]

We have a link to our access database on our website. The .mdb file resides
in the folder that contains all the files for our website, and is on a shared
drive. This is meant to allow users to add and update records. Problem is,
when the link is clicked, apparently Access opens a version of the database
and places it on the user's C: drive. Additions and changes are then stored
in the version on the user's pc, and not in the version on the shared drive.

Does anyone know how to overcome this so that changes are made to the main
file on the server? Thanks in advance...

 

[Granny Spitz via AccessMonster.com]

Additions and changes are then stored
in the version on the user's pc, and not in the version on the shared drive.

Then it's working like it should, hon. Access is a desktop database, not a
web database. You can split the database and keep the back end (tables and
relationships) on the shared drive and put a copy of the front end (queries,
forms etc.) on each user's desktop. If you want the users to add or change
records from the web, you need to build a web application that connects to
the database tables. Most commonly used is ASP, ASP.Net, Macromedia,
Frontpage etc.

 

[Norman Yuan]

I assume the said website is an internal one and siad link is on a web page.
When uer click a link on a web page, the browser send an http request to the
web server, then the web server do something and send a http response back.
Usuallu the response is texts with HTML formatting tags. If the requested
file is not a staic/dynamic html content, the web server, in most cases and
if it is allowed, will grab the file and streaming back to the browser. In
this case, the browser would display a Download/Save dialog box for user to
save the file coming from the web server.

So, what you described is how web server works. In other word, your setup
for using/sharing the Access database is wrong.

Usually, you make two parts for an Access database application. The
front-end that installed on all users' computer and the back-end that
contains data and locates on a network share, which is accessible to users.
Then you link the front-ends to the back-end. If the database has to be
shared through web server, you need build a web application to access
(indirectly) the data in a access database (*.mdb), although *.mdb may not
be good choice as data store on the web (internal or public).

 

[aaron.kempf]

I tink that she's talkignn about 'right-click IMPORT HTML' from within
a MDB

I wish that it worked better also; I use it all the time and Im
frequently frustrated that it works like crap; but I guess that MS
doesn't have the MONEY to start taking QUALITY and RELIABILITY
serioiusly

 

[Guest]

Thanks, Granny...that was really helpful! And since we already have an .asp
page that uses that same db, we can just copy that and make adjustments.
Should have thought of that in the first place!

 

[Granny Spitz via AccessMonster.com]

Thanks, Granny...that was really helpful! And since we already have an .asp
page that uses that same db, we can just copy that and make adjustments.

You're welcome, Katie. Sounds like a good plan to me!