Dear friends,

Have anyone isolate "thephile" forum and put that to work on access 
database ?

If yes, please share the code ;P

Note: If you know any forums that work in access database, please post 
the link ;+

Thanks

Best regards,
Ricardo Figueira

Ricardo Barros Figueira wrote:
> Have anyone isolate "thephile" forum and put that to work on access
> database ? 

I wouldn't personally convert to a Jet (Access) database.  (Especially
when reasonably priced SQL Server hosting is available.)

If you go that route I'd STRONGLY recommend performance testing at your
expected loads, on your expected machine before going live.  (WAST (Web
Application Stress Tool? Formerly called Homer) is free from Microsoft,
or the tool in Visual Studio.NET (ACT in some editions) may be available
to you.)  If it doesn't hold up you can abandon it before you even
launch.

Jet databases can perform better than many people suggest but there are
limits.

Mike Gale, Decision Engineering (NZ) Ltd.

PS.  I also suggest that if you cannot write the code, stored procedures
(queries) etc. yourself,  you should make sure you have ready access to
suitable skills (for when you have a problem).

Mike,

Thanks for your opinion ;P

The problem is that i dont have money to host my forum / website with 
SQL Server.
Besides that, is for using in my Portuguese DotNet List (we are now 120 
portuguese programmers) .... yup... i am Portuguese ;P
I am working on website, for my dotnet list (PontoNetPT), and i want to 
put an forum (message board) BUT must to be in Access Database.... i 
will try to host my list site on FREE host like 
http://www.brinkster.com/. I now that is not a very good soluction, but 
is the best i can get !

If anyone have one forum with access database, please share ;P
Thanks !

Best regards,
Ricardo Figueira (RBFIGUEIRA)


-----Original Message-----
From: Mike Gale [mailto:info@d...]
Sent: quinta-feira, 12 de Setembro de 2002 20:38
To: Website Programming with ASP.NET
Subject: [aspdotnet_website_programming] RE: Forum (access)


Ricardo Barros Figueira wrote:
> Have anyone isolate "thephile" forum and put that to work on access
> database ?

I wouldn't personally convert to a Jet (Access) database.  (Especially
when reasonably priced SQL Server hosting is available.)

If you go that route I'd STRONGLY recommend performance testing at your
expected loads, on your expected machine before going live.  (WAST (Web
Application Stress Tool? Formerly called Homer) is free from Microsoft,
or the tool in Visual Studio.NET (ACT in some editions) may be available
to you.)  If it doesn't hold up you can abandon it before you even
launch.

Jet databases can perform better than many people suggest but there are
limits.

Mike Gale, Decision Engineering (NZ) Ltd.

PS.  I also suggest that if you cannot write the code, stored procedures
(queries) etc. yourself,  you should make sure you have ready access to
suitable skills (for when you have a problem).

Ricardo Barros Figueira wrote:
> If anyone have one forum with access database, please share ;P
> Thanks !

I haven't seen any replies so here are a few observations that may help
if you're doing it yourself:

1)  I wrote a few (less than 3) ASP apps. that could switch between Jet
and SQL server.  In part they generated "dynamic SQL" which presented a
few issues as the SQL syntax differs.  The issues were easy to handle.
This stuff worked great.  (But I found the compatibility usually wasn't
needed in my situation.)

2)  Jet 4 has a little publicised feature which enables you to read and
write "stored procedures".  The procedures are not as fully featured as
SQL stored procedures (they are simply Jet queries).  This could be
useful.  The facility had one major shortcoming (that I remember).  You
could not use it to enumerate the "stored procedures" available so you
had to write some infrastructure yourself!!

3)  I expect an automated routine to take simpler SQL queries and load
them into Jet is rather easy to create.  Doing it this way might even be
quicker than converting each "query / SP" by hand!  You could also
"partially automate".  That is create a text file from SQL Server sp's,
edit by hand (if needed) then take that file and inject it into Jet!

4)  With 120 potential helpers you should be careful to only collaborate
with one or two on the project!!  (Otherwise you hit that thing: 1
programmer 10 days, 10 programmers 15 Days (150 man days) and 50
programmers you never get the job done!)

5)  Hopefully you can keep the code compatible between SQL Server and
Jet.

If you decide to go this route I'd love to hear what you find.

Good luck.

Mike Gale, Decision Engineering (NZ) Ltd.