Database Problems. Please Help!

[LW]

We have been trying to display our Access Database
information on our Intranet, and enable users to search by
different fields. We do not want anyone to update through
the Intranet. The updating is done directly by one person
into the Access file. Something seemingly easy has been a
nightmare. This is what we have been trying:

1. Using Front Page's Database Results Wizard, we have had
to first import our database into our Intranet web, and
then we can see records, and search etc. However since
this database is updated elsewhere, we can't keep
reimporting the file to keep the info dynamic, and it will
not open the imported Access file in its web location for
editing.

2. Using Access's data access page feature, we have been
able to get our records to show up on the Intranet and be
connected to the underlying file. In addition we have been
able to seal records from user editing, but the problem is
that only search capabilities are a weak filter by
selection that does not do wildcard searches (such as one
word in a description field).

3. In our Access database we have a perfect setup of
parameter queries so that the user inputs all or part of a
reference and gets a nice report. When we get this into
our web thru a data access page, the parameter form does
come up, but after filling it in, records never show in
the report.

It seems we have come up against specific stumbling
blocks. For instance, does anyone know how to set up a
hyperlink on a page created in Front Page that would just
bring up and transfer control to the Access file? Right
now, "Quick View" gibberish comes up.

Does anyone know how can I reference an Access database
outside of the Intranet in a file such as global.asa? It
only appears to recognize http:// and not network letters?

Any help would be appreciated since we have been pulling
our hair out!

 

[Kevin Spencer]

Access is not designed for Internet use. As such, it CAN be used in an
Internet web site, but has some problems. Some of what you've described
falls into that category (#1, for example). #2 and #3 are due to lack of
knowledge of the technologies of ASP, ADO and the SQL language.

Using a true database server, such as SQL Server, would enable you to use
the same database for your web site as you use for your office, and you
could create Access Database Projects (.adp) to enable your workers to work
with the SQL Server database in a familiar Access interface.

Databases are complex animals, mostly due to the fact that they are used for
so many different purposes. A database is, after all, simply a repository
for data. And data can be anything that you can translate into 1's and 0's,
which is almost anything. The FrontPage database tools allow you to perform
a small number of the most commonly-used functionality in a database. Once
you start to get a little bit more specific about your particular
requirements, some knowledge of ASP, ADO, and the SQL language are
necessary. The farther out you go from "the norm" the more programming
experience you need.

--
HTH,
Kevin Spencer
..Net Developer
Microsoft MVP
Big things are made up
of lots of little things.

 

[LW]

Thank you so much for your very informative response. I
am looking into working with a person who has this
expertise.