I created a data access page and the .mdb on my Win98 local disk
using Access 2000 and tested it locally, it worked well. Then I ftp the data access page and the .mdb file to web server(it's my school's server). But when I tried to access that web page from explorer 6.0, it gave me
an error message "Safety settings on this machine prohibit accessing a
data source on another domain". How to make the page work on the server?

Environment: Win98, Access 2000, Explorer 6.0

Thanks!

Well, I'm assuming you mean that the "data access page" is your webpage that accesses the data source (the database in this case). Unless you're using a Connection String that uses the Server.MapPath to find the DB, there is no DSN setup on the School server to access the database.

I recommend contacting the school network admin and telling them:

A. Where the DB is located
B. A username and password to connect to it;

From there, the school server will now have a local DSN to connect to the DB. If they don't allow DSNs, you'll have to make a connection string. Just to let you know as well, Access databases were never designed to be online DB's. They can't handle much more then 1 or 2 people at a time. You may want to look into mySQL or SQL itself.

hi aegiskleais,
thanks for your quick reply!

I disagree about the access connections, In my understanding it is capable of handling around 100 connections at a time, and although it was not meant to go online, it's easy to use and learn, very cheap and can be upto 2gb in size.

As to the "data access page", if you are referring to the built in access function then i would change it to a dynamic page in UD, you'll find it much easier.

"Nobody ever said this stuff was easy"

Yep, i agree that Access 2000 works quite nicely on the web with lots more than one or two users, in fact one site we knocked up in UD and Access is getting over 750 visitors a day and is operating sweetly!!

Does anyone know if there is any benefit in creating an MDE file instead of the MDB?

CHeers
Leed


:: Son, im Thirty.... ::

Edited by - leed on 21 Jun 2002 11:18:55

Well, this is bad news to me.

We're on some POWERFUL servers (lets just say it's a popular game company), and yet it takes WELL over 40-50 seconds for the UD code and an ASP DB connected via a Connection String to validate the user. I mean, that's PITIFUL. I about timeout in my login session before it even replies.

Setup a system with mySQL and it's 2-3 seconds at worst.

I also have a website running on a access db that gets well over 500 hits a day. It is still running very fast.
My host is hostonce.com


My two cents,

fliquid

Here you go guys some info about using Access as a Web database:

www.15seconds.com/issue/010514.htm

Access' performance is much improved if you use an OLEDB connection instead of an ODBC system DSN. Incidentaly this goes for SQL Server too.

www.powerasp.com/content/database/dsn_vs_dnsless.asp

Bear in mind that the limitations are for concurrent connections, so if you are opening a recordset, displaying the data then closing the recordset, this takes only a fraction of a second, so you could probly handle several hundred users an hour before you run into trouble.

500 users a day, if spread over 12 hours is roughly 40 an hour, less than one a second. So the chances that 10's of users access the same page at the exact same time using the same recordset connecting to the same database table and creating multiple concurrent connections is fairly slim.

Regards

Owen.

Multiple Parameter UD4 / Access 2000 Database Search Tutorial:
www.tdsf.co.uk/tdsfdemo