Dreamweaver - Slow database Access

Author

Slow database Access

Rajiv Vaishnav

2006-02-26, 3:14 am

Hi there,

I have a table which has 750 records.

When I try to populate in dependent dropdown, it takes long to load the
page, I am using Kermy Dynamic dropdown. Why it takes so long to open the
asp page.

Is there a problem with access database or with kermy dynamic dropdown,
kinldy help.

Rajiv Vaishnav

2006-02-26, 3:14 am

I dont understand your answer

"Bonnie" <"kroko[Occam]"@sbcglobal.net> wrote in message
news:dtrbnb$qfd$1@forums.macromedia.com...
> Rajiv Vaishnav wrote:
> Are you determined to ignore all the advice you have already been given on
> this issue? :-/
>
>
>
> --
> Bonnie in California
> kroko at
> sbcglobal dot net
> http://www.theanimalrescuesite.com/...ts/CTDSites.woa

Bonnie

2006-02-26, 3:14 am

Rajiv Vaishnav wrote:
> Hi there,
>
> I have a table which has 750 records.
>
> When I try to populate in dependent dropdown, it takes long to load the
> page, I am using Kermy Dynamic dropdown. Why it takes so long to open the
> asp page.
>
> Is there a problem with access database or with kermy dynamic dropdown,
> kinldy help.
>
>
>
Are you determined to ignore all the advice you have already been given
on this issue? :-/

--
Bonnie in California
kroko at
sbcglobal dot net
http://www.theanimalrescuesite.com/...ts/CTDSites.woa

Bonnie

2006-02-26, 3:14 am

Rajiv Vaishnav wrote:
> I dont understand your answer
>here is my actual tables, pls guide me how to write the query.

You will need to create an alias of the Worker table for every instance
referenced in the Master table, then join each of those in the query.
This is
going to be very ugly and probably perform terribly.

Your database design is bad. You really need to listed to the others and
create a relation table or hire someone that knows more about database
design.
You are currently going down a very bumpy road and it will only get worse.

=====

Rajiv Vaishnav wrote:
[color=darkred]

Sorry Rajuv, I *can't* help any further. You're heading down a dead-end
road
which is only going to cause you lots of problems. As bregent says,
there is
a solution, but it's messy, clunky and will cause lots of problems.

You really will make much faster progress if you take a step backwards and
learn more about how a relational database wants to work, and redesign your
database to accomodate this.

Have a read of http://www.databasejournal.com/sqle...cle.php/1469521
for
a good run down of what a relational database can do for you and what
normalisation is used for.

There is also a newsgroup (news://microsoft.public.access) where you'll be
able to gain more specific help.

HTH,

Pete.
-- Peter Connolly http://www.acutecomputing.co.uk Derby UK Skype ID:
acutecomputing

--
Bonnie in California
kroko at
sbcglobal dot net
http://www.theanimalrescuesite.com/...ts/CTDSites.woa