FP2003 and databasing

[Uncle Joe]

Bought FP2003 last night but haven't taken it out of its plastic box
yet.
All the new features, plus the mystery of SharePoint, confuses me.
I cannot find simple explanations/examples for SharePoint. Was
comfortable with the old server extensions.

I last used FP2000, and FP2003 has become infinitely more complex
than my last old web site consisting of static text pages.

I want to create a new, highly active 70-topic discussion web based on
my
own template. 70 pages + home page, + 70 databases. Want visitors to
enter
comments, which would then become part of that topic's database and
displayed
a few minutes later in the appropriate topic's screen.

My main question is this: what kind of FP2003 compatible database
scheme should I use to support my new discussion web? I need to
use a reliable, fast database which allows me to delete records at
will (offensive language, spam, fighting words, and HTML.) and
to archive databases.

Your assistance would be appreciated. Thank you.

Uncle Joe

 

[Stefan B Rusynko]

FP 2003 will support Access DB (simplest to use) under a online Site hosted on a Windows Server running the FP SE
- no different than FP 2000 as far as support there
- you will not need the features of WSS (SharePoint services)

It will, in a very limited way create, your DB and allow you to use the DBRW or DBIW to display or edit your database
- but it will not do what you want unless you learn how to hand code is ASP

PS
70 DB is not the best solution for 70 topics
- maybe 1 DB w/ 1 table keyed to 70 topics is
Depending on your server Search for ASP. ASP.net or PHP Forum templates which will do what you want
--




| Bought FP2003 last night but haven't taken it out of its plastic box
| yet.
| All the new features, plus the mystery of SharePoint, confuses me.
| I cannot find simple explanations/examples for SharePoint. Was
| comfortable with the old server extensions.
|
| I last used FP2000, and FP2003 has become infinitely more complex
| than my last old web site consisting of static text pages.
|
| I want to create a new, highly active 70-topic discussion web based on
| my
| own template. 70 pages + home page, + 70 databases. Want visitors to
| enter
| comments, which would then become part of that topic's database and
| displayed
| a few minutes later in the appropriate topic's screen.
|
| My main question is this: what kind of FP2003 compatible database
| scheme should I use to support my new discussion web? I need to
| use a reliable, fast database which allows me to delete records at
| will (offensive language, spam, fighting words, and HTML.) and
| to archive databases.
|
| Your assistance would be appreciated. Thank you.
|
| Uncle Joe
|
|
|

 

[Bob Lehmann]

Before you go around "databasing" with FP, or any tool for that matter, it
may behoove you to learn a little bit about DB design.

What you describe could be done with 1 or 2 web pages, 1 database, and
handle unlimited discussion topics.

Bob Lehmann

 

[Uncle Joe]

The purpose of writing this topic was to obtain recommendations on
which specific type
of database would be the most productive, fast, and efficient one for
serving hundreds of
simultaneous reader requests using FP2003. I'm coming the conclusion
that one database
(keyed on state/timestamp might do the trick, but putting all my eggs
in one database makes
me nervous.

I have yet to find a good tutorial on database design or for using
databases with FP2003.

I do not grasp your contention that only 1-2 pages could service 70
distinct topics (i.e.,
Alabama, Missouri, and Texas) bloggers at the same time. What about
the headings? What
about the embedded code in each page's header to acquire/display only
the blog entries for
that state.

Thanks for your input.

 

[Stefan B Rusynko]

Serving 70+ topics in just several pages w/ different content, function, and look would come all from the DB and ASP coding if done
correctly
- but it can't be done w/ just wizards
- it would require learning ASP (or PHP) or using a template

With just hundreds of users you could use Access & ASP (if your host supports it)
Search for ASP forums in Google - like http://forum.snitz.com/




| The purpose of writing this topic was to obtain recommendations on
| which specific type
| of database would be the most productive, fast, and efficient one for
| serving hundreds of
| simultaneous reader requests using FP2003. I'm coming the conclusion
| that one database
| (keyed on state/timestamp might do the trick, but putting all my eggs
| in one database makes
| me nervous.
|
| I have yet to find a good tutorial on database design or for using
| databases with FP2003.
|
| I do not grasp your contention that only 1-2 pages could service 70
| distinct topics (i.e.,
| Alabama, Missouri, and Texas) bloggers at the same time. What about
| the headings? What
| about the embedded code in each page's header to acquire/display only
| the blog entries for
| that state.
|
| Thanks for your input.
|
|
| | > Before you go around "databasing" with FP, or any tool for that
| > matter, it
| > may behoove you to learn a little bit about DB design.
| >
| > What you describe could be done with 1 or 2 web pages, 1 database,
| > and
| > handle unlimited discussion topics.
| >
| > Bob Lehmann
| >
| > | >> Bought FP2003 last night but haven't taken it out of its plastic
| >> box
| >> yet.
| >> All the new features, plus the mystery of SharePoint, confuses me.
| >> I cannot find simple explanations/examples for SharePoint. Was
| >> comfortable with the old server extensions.
| >>
| >> I last used FP2000, and FP2003 has become infinitely more complex
| >> than my last old web site consisting of static text pages.
| >>
| >> I want to create a new, highly active 70-topic discussion web based
| >> on
| >> my
| >> own template. 70 pages + home page, + 70 databases. Want visitors
| >> to
| >> enter
| >> comments, which would then become part of that topic's database and
| >> displayed
| >> a few minutes later in the appropriate topic's screen.
| >>
| >> My main question is this: what kind of FP2003 compatible database
| >> scheme should I use to support my new discussion web? I need to
| >> use a reliable, fast database which allows me to delete records at
| >> will (offensive language, spam, fighting words, and HTML.) and
| >> to archive databases.
| >>
| >> Your assistance would be appreciated. Thank you.
| >>
| >> Uncle Joe
| >>
| >>
| >>
| >
| >
|
|