Hi there,

I'm using FP 2003 and Access 2003 (I know, I know, but I'm required to
use Access). Recently I noticed some of my pages were timing out when
I was contacting the database. I tried a test and here's what I
found.

Database connection: System data source on webserver
Data: Table with two columns and about 15 rows

A. I created a new form with a text box where I enter a number. That
form calls query.asp which is nothing but a database results wizard
insert table with the query "SELECT * FROM "_Cost Center" WHERE Number
LIKE ::Number::" (Remember, * is just two columns.)

This page constantly times out. I.e., the script times out. I don't
want to increase the timeout because, in my opinion, this shouldn't
take 2 minutes!

B. I created a second ASP page that uses Perlscript to do the same
query and display the results instantaneously.


I've never had this problem with the Database Results Wizard before
and can't find anything wrong. Other than Perl, I don't do much
scripting. It's supposed to be a simple search, so the DRW is perfect
and easier for me than perlscripting all the text box entries, etc.

Does anyone have any idea what could be causing this?

Thanks for anything you can offer.
-Diana

The " surrounding cost structure could be breaking things. Database tables
shouldn't have spaces in their names so that could be an issue. Try
enclosing _Cost Center in brackets instead as [_Cost Center].

Also, you're using a LIKE comparison without using any wildcards. That means
it's essentially an equality. Like is best used when you're comparing
textual data and you want to match part of the data using wildcards. Try
using a simple = instead of the LIKE as that's a less costly operation for
Access.


--
Hope this helps,
Mark Fitzpatrick
Former Microsoft FrontPage MVP 199?-2006

"Diana" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hi there,
>
> I'm using FP 2003 and Access 2003 (I know, I know, but I'm required to
> use Access). Recently I noticed some of my pages were timing out when
> I was contacting the database. I tried a test and here's what I
> found.
>
> Database connection: System data source on webserver
> Data: Table with two columns and about 15 rows
>
> A. I created a new form with a text box where I enter a number. That
> form calls query.asp which is nothing but a database results wizard
> insert table with the query "SELECT * FROM "_Cost Center" WHERE Number
> LIKE ::Number::" (Remember, * is just two columns.)
>
> This page constantly times out. I.e., the script times out. I don't
> want to increase the timeout because, in my opinion, this shouldn't
> take 2 minutes!
>
> B. I created a second ASP page that uses Perlscript to do the same
> query and display the results instantaneously.
>
>
> I've never had this problem with the Database Results Wizard before
> and can't find anything wrong. Other than Perl, I don't do much
> scripting. It's supposed to be a simple search, so the DRW is perfect
> and easier for me than perlscripting all the text box entries, etc.
>
> Does anyone have any idea what could be causing this?
>
> Thanks for anything you can offer.
> -Diana
>

Thanks, Mark. I'll give it a try.


And, ooops, I didn't realize I posted this question twice. Sheesh.