If you know how to develop using Access using some VBScript (and don't need
to update the database by opening it directly while it is expected to serve
data) then you will be ok if you go out and get a book on ADO and ASP -- or
if your brave you can dive into ASP.NET using the Microsoft Visual Studio
suite.
If you want serious developer tools and gigs of documentation then you could
look into using the free MSDE data engine as your database and use access to
connect to it using the Access Project. MSDE is also on the later Office
CD's and sounds like it would work just fine for your application. If this
is going to get big and crazy, you can detatch and reattatch the data files
to the full blown SQL Server product - it's easy to do, on purpose. If you
want to know why I prefer not to use mdb's for the web, read on - this is
something I know a lot about... If you need help or a place to serve your
site with these technologies, I can do that. If you already have a place -
cool, just do a lot of reading and testing...
<Php and Linux is cool - but watch out for the proprietary lawsuit letters
from SCO/Unix that Linus sent out. :) I understand some things about
Linux - trust me, but hey - America is free enterprise baby, and Microsoft -
well they just do it better than others. So, all you Linux people - don't
have a cow over this! You may have your turn sometime and you can't live on
donated pizza forever (cholesterol will get you) so give it up.>
Previously posted at Microsoft.public.dotnet.framework.aspnet...
I have built many ASP websites using mdb backends and have had downtime. I
haven't even tried it with ASP.NET because I learned EARLY. If you open the
database and try to modify it, users will "sometimes" get a "Page cannot be
displayed" error because you have the database locked. In early versions of
IIS, closing the database would still not release the locks for some reason.
The only way I could get it back online was to stop IIS and copy, then
rename the mdb, then restart IIS - unbelievable... so... I resorted to
copying the thing elsewhere, modify it as fast, then replace the production
mdb. Hopefully, you are not collecting data while this is going on or else
it would obviously be lost. Sure, you could import some of the changes, but
geez...
On both mdb releases I had instances where ISP administrators did a blanket
permission assignment and gave all web files "read only" thinking that they
were "just html files". That certainly doesn't set well with a mdb.
Using Sql Server (or MSDE) is wonderful, I have dozens of sites running with
it and
wouldn't think twice about changing anything. Once you set up the
permissions and connection string, it's very unlikely you will ever have to
look at that again unless the entire server changes somehow.
But really, too many Access things like this to list... small database or
large, this is Access and you pay with frustration for keeping things simple
with one little mdb.
--
Jerry Boone
Analytical Technologies, Inc.
http://www.antech.biz
Secure Hosting and Development Solutions for ASP, ASP.NET, SQL Server, and
Access
"Inquest750" <in********@excite.com> wrote in message
news:4d**************************@posting.google.c om...
Can anyone tell me where I can get instructions to design an Access
database to work directly with a website? The website will hopefully
contain a member base and that is what i would use access for. The
databases purpose is to collect all the information that i would
require for new members to enter upon registration... The database
would also need to be connected to to verify users logging in of
correct usernames and passwords....has anyone done this? know anything
about it? know where i could possiblyget answers or a different
solution?
