The web server is running IIS3.0. The database may or may
not be run on the same system. That decision has yet to
be made.
I am carrying out reasearch for a company I have created
an online handbook for, and I have suggested creating a
database to allow some of the documents that they have to
be live documents that don't have to be uploaded each time
changes are made. I understand by using ASP pages it is
possible to make changes to the data within the database,
and by refreshing the Web within your browser any changes
will be available to the client PC.
The database would also be used to integrate some other
things for the company such as staff directories, price
lists, supplier lists to name but a few.
The company would like something that would last them well
into the future, rather than giving a temporary fix.
In terms of cost this has not been discussed as yet, but
as part of my research that is what I need to report back
to the senior management of the company.
I would not be creating the database myself. It would be
outsourced to an external company for the design and build
work to be completed. I have been using FrontPage for the
last 3 months, and have created a simple database in
Access, but I am wondering whether this will be the right
tool for the job.
I want it to appear seamless to users that they are
accessing the database through the FrontPage online
handbook I have created, so that as far as they are
concerned the interface is the same.
The company has around 25 users, split between New Zealand
and Australia.
-----Original Message-----
What web server are you using? Are you going to run the database on the
same system?
You could use MySQL which is free at
http://www.mysql.com and runs on just