Results 1 to 2 of 2
  1. #1
    4 Star Lounger
    Join Date
    Apr 2002
    Northern Territory, Australia
    Thanked 0 Times in 0 Posts

    database backend on Web (Access 2003)

    I have been working with back end / front end databases for a while now. I have also used replication.

    However, I am not very familiar (yet) with putting anything on the Web except for publishing things on our work Intranet using their publishing tool.

    I have been wondering if it is possible to put my database back end on the internet or the intranet and link a front end to it without getting too complicated? Any ideas or discussion would be appreciated.

  2. #2
    4 Star Lounger
    Join Date
    Jan 2002
    Brookings, South Dakota, USA
    Thanked 0 Times in 0 Posts

    Re: database backend on Web (Access 2003)

    Hi Kerry,
    First, you can use an Access back-end for web based apps and it doesn't have to reside on the web server, but that is way more problematic "Why can't I access......", so it'd probably be best if the back-end did reside on the web server. Then you can still link to your back-end via the same linking you'd be used to; i.e. UNC, mapped drive, etc. Then in your web pages, you'd use ADO/ADO.NET to access the data stored in that back-end.
    That said, it is highly recommended (at times vehemently so) that you do not use Access for web apps. Here are 2 takes on that: ASPEmporium; ASPFAQ. I still have a couple of intranet sites using Access as the database, but the data is NOT proprietary or sensitive, and the webpages are not hit that often.
    I've been using SQL Server 2000 (we're in the process of upgrading the entire university to SQL Server 2005) and most recently SQL Server 2005 Express for any new web apps. I can then use an ODBC connection on whomever's machine who is required to have an Access front-end. To me this is the best of both worlds. I can still use DAO to manipulate the data to anyone's heart's content and I've got the power of sql server behind it. Of course there are some issues relating what SQL Server uses as datatypes as compared to what Access uses and a couple more idiosyncracies, (See <post:=593,489>post 593,489</post:> along with the links included to get an idea what those may be) but those are really inconsequential after you've worked around them a time or two.
    Hope this helps a little.
    <IMG SRC=>
    "Those who dance are considered insane by those who can't hear the music" - George Carlin

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts