| | |
|
|
|
Re: Using DW for ASP |
|---|
| message from Leesa on 22 Jul 2004 |
From what I understand Access does pretty well as long as the only person
accessing it is the owner doing updates with an html back end. Once you start
getting multiple people accessing the db at the same time (like many people
submitting ads at the same time to the db) is when access can't handle it. It
is designed as a desktop db for single user access. That's what I use MS
Access for.
It's easy to learn using DW & Access so you might want to just use it as a
stepping stone and learn php & MySql.
Good luck.
|
| Murray *TMM* replied to Leesa on 22 Jul 2004 |
Access can handle more than that, but it doesn't scale gracefully. I
believe that the magic number is in the range of 5-10 hits on the same
record at the same time. If you are expecting that much activity, then you
will need to use SQL technology.
|
| Durwood Edwards replied to Murray *TMM* on 22 Jul 2004 |
We're surprised if any database available on line gets more than a dozen
hits per day. Nothing of what we are doing requires us to reach for the
Oracle.
I haven't seen activity cited as a possible culprit for the error we are
getting. It is a memory leak thing and remains a mystery and irritant.
D
"Murray *TMM*" <forums@HAHAgreat-web-sights.com> wrote in message
news:cdoh05$r6s$1@forums.macromedia.com...
|
|
Archived message: Re: Using DW for ASP (Macromedia Dreamweaver Web Design)
