PH Web screen timing out

[Edis, Bob]

G'day all 

Environment:
PowerHouse Web 2.21D3
PowerHouse 4GL 8.21D4
Windows NT 4.0 sp6
MS SQL Server 7.0 sp3
IIS 4.0

We have a PH Web screen where the user can enter a search value in any one
or more of four fields to find customer records.  The most typical scenario
is enter all or part of a customer name and then click on the Search (Find)
button.

This screen was taking an abnormal amount of time to return each set of 10
records on the results page and was timing out after about 4 pages.  There
was no index on the customer name column so one was added.  In addition to
this we added ACCESS statements after the FILE statement to make the Find
procedure use the indexes.  The result was a dramatic improvement in
response time.  Here is the new syntax:

FILE customer IN dwdb PRIMARY                                        &
     HTMLKEY customer_key                                            &
     HTMLFIELD customer_key, customer_id, name
  ACCESS VIA customer_id USING customer_id REQUEST customer_id
  ACCESS VIA name        USING name        REQUEST name 
  ACCESS VIA corp_cust_id USING corp_cust_id REQUEST corp_cust_id
  ACCESS SEQUENTIAL ORDERBY name

Then results page has the customer_key column hilighted.  The user has to
click on this column in the desired record from the results set to bring
that record's data into the screen fields. Customer_key is the primary key
on the table and is contained in a unique index.  This is the procedure used
in our screens to reload the screen with the returned data.  It normally
works great.

PROCEDURE POSTPATH
BEGIN
  IF  PROMPTOK FOR customer_key OF customer                          &
  AND t_flag NE "Y"          
  THEN BEGIN
    LET t_flag = "Y"
    DEFER LINKSCREEN cc_customer                                     &
          ACTION "loaddata"                                          &
          PASSING customer_key, t_corp_cust_id, t_flag
  END
END

The problem is that the screen times out after about 2 minutes when trying
to retrieve the table row after the customer_key column has been clicked.

Anyone out there have an idea where the bottleneck could be?

Regards,

Blue