don't listen to anyone that lets you use a MDB file in an web
environment.
if you used Access Data Projects; you wouldn't need to rewrite your
database
learn ADP and use DAP if you must.
MDB is a joke though; the most ridiculous db engine EVER.
-Aaron
Bob Alston wrote:[color=blue]
> Phillip Windell wrote:[color=green]
> > "Visitor No 3" <ThisIsNotMyAddress@Yahoo.co.uk> wrote in message
> > news:129dcq9mel9cp03@corp.supernews.com...
> >[color=darkred]
> >>I have developed the odd Access Application in VBA but I have never used[/color]
> >
> > VB
> >[color=darkred]
> >>or VBScript, which seem to be the tools for ASP.
> >>
> >>My question, before I start, is: Is this a sensible route to take and my
> >>other question is: Can ASP be programmed in VBA, with which I am familiar.[/color]
> >
> >
> > VBA has absolutely nothing to do with ASP. ASP is a "platform" that runs on
> > Microsoft's Internet Information Server (IIS). It interprets VBScript,
> > JavaScript, JScript, and serveral others although the popular choice is
> > VBScript. It runs only on the server and has nothing to do with the User's
> > browser.
> >
> > The MDB is kept on the Web Server "outside" of the Web Path, and the folder
> > it is kept in, and the MDB file, must have read/write permission granted to
> > the Web Server's local IUSR account. Here is an example:
> >
> > c:\wwwroot\visitorNo3Site
> > |
> > --website
> > |
> > --database
> >
> > 1. The Web Path (root of the website) is set to the folder "website".
> > 2. The FTP Path (root of the FTP service) is set to "visitorNo3Site". This
> > lets you upload files to any folder
> > 3. The IUSR account is given read/write to the folder "database"
> > 4. Users going to the site come "in" at the folder "website" and cannot get
> > to the other fiolders, so they cannot "steal" or mess with the MDB file
> > located in folder "database"
> > 5. The ASP engine running on the webserver itself, using the IUSR account,
> > is able to get to the "database" folder and read the contents to build the
> > web pages from the data and send them to the user's browsers
> >
> > You do *not*..... "access the MDB over the web".
> > You maintain a local copy of it just like you maintain a local copy of the
> > website's files. In the same way that you would make changes to the local
> > web site files then upload them to the server to update the site,...you do
> > it the same way with the MDB file,...the MDB file is treated and worked with
> > exactly the same way as any other site file like *.html, *.asp, whatever.
> >
> > It is possible to design an "Admin" web site that runs along side the
> > "public" one that can be used to make changes to the MDB file directly where
> > it is at,...but often this is more trouble than it is worth (unless you are
> > a highly skill professional at this) and will not easily work in all
> > situations.
> >
> > None of your questions are really "Access" questions. They are ASP
> > questions,..you need to ask in one of the ASP groups like:
> >
> > microsoft.public.ineserver.asp.db
> >
> > You are dealing with ASP Classic,...this is *not* ASP.Net,...don't go to the
> > ASP.Net groups with this,...the two are no where near the same thing.
> >[/color]
> Take a look at my web site for info on how to utilize Access/Jet
> databases in a web environment:
>
>
http://webpages.charter.net/bobalsto...20Internet.htm
>
>
http://webpages.charter.net/bobalsto...onSoftware.htm
>
> Bob[/color]