What is the limit of REQUESTS in a QTP run?

[Deskin, Bob]

Given that the maximum number of files in a RUN is 63, and the fact that
in QTP, every REQUEST must have an ACCESS statement, that gives a
maximum of 63 REQUESTs in a RUN. But in practical terms it will probably
be less unless the RUN is just for editing.

Bob

-----Original Message-----
From: powerh-l-bounces+bob.deskin=cognos.com at lists.sowder.com
[mailto:powerh-l-bounces+bob.deskin=cognos.com at lists.sowder.com] On
Behalf Of shulbert at clblf.com
Sent: December 6, 2005 5:05 AM
To: fernando.olmos at hpa.com.au
Cc: powerh-l at lists.sowder.com
Subject: RE: What is the limit of REQUESTS in a QTP run?


RTFM

<qtpmanual page=32>
Limit: A maximum of 31 record-structures, including subfiles, can be
declared in a request. A maximum of 63 record-structures can be declared
in a run. There can be a maximum of 1,023 items per record structure.
</qtpmanual>

although, some platforms count file handles and not record structures,
and indexed subfiles count as two. and qtp may not count a second,
aliased, reference to a record structure as separate. some versions of
qtp were also a bit fuzzy as to the exact maximum number of files
allowed open, but as far as i know this is no longer the case.

your mileage, therefore, may vary.

so, to answer your question, it looks like you can have sixty output
statements in a run, two requests with one table in the access
statement, each with thirty output statements.

but if you use an access statement to reference a pl-sql code block all
bets are off.

regards,
stephen.



 -----Original Message-----
From: 	fernando.olmos at hpa.com.au [mailto:fernando.olmos at hpa.com.au]
Sent:	Tuesday, December 06, 2005 4:02 AM
To:	richard.latimer at airways.co.nz
Cc:	powerh-l at lists.sowder.com
Subject:	RE: What is the limit of REQUESTS in a QTP run?

Actually the limit, is as you stated Richard 31.

The number of requests is unlimited, but the number of OUTPUTs on a
single QTP RUN, is limited to 31.

Damn!

Thanks

-----Original Message-----
From: richard.latimer at airways.co.nz
[mailto:richard.latimer at airways.co.nz]
Sent: Tuesday, December 06, 2005 2:27 PM
To: Fernando Olmos; powerh-l at lists.sowder.com
Subject: RE: What is the limit of REQUESTS in a QTP run?


Fernando,

I think it is file based.

I have an edit process that writes to aliases of a single subfile and
have a note in the header that tells me I must keep the number of
outputs per REQUEST to <= 30 and the number of outputs per RUN to <= 60.
Sorry but I can't remember where I found the reference (PH607F on
AS/400)

cheers
Richard


**********************************************************************

This electronic message together with any attachments is confidential.
If

you receive it in error: (i) you must not use, disclose, copy or retain

it; (ii) please contact the sender immediately by reply email and then

delete the emails. Views expressed in this email may not be those of the

Airways Corporation of New Zealand Limited

**********************************************************************



**********************************************************************
IMPORTANT
The contents of this e-mail and its attachments are confidential and
intended solely for the use of the individual or entity to whom they are
addressed.  If you received this e-mail in error, please notify the HPA
Postmaster, postmaster at hpa.com.au, then delete  the e-mail. This
footnote also confirms that this e-mail message has been swept for the
presence of computer viruses by Ironport. Before opening or using any
attachments, check them for viruses and defects. Our liability is
limited to resupplying any affected attachments. HPA collects personal
information to provide and market our services. For more information
about use, disclosure and access see our Privacy Policy at
www.hpa.com.au
**********************************************************************
-- = = = = = = = = = = = = = = = = = = = = = = = = = = = = Mailing list:
powerh-l at lists.sowder.com
Subscribe: "subscribe" in message body to
powerh-l-request at lists.sowder.com
Unsubscribe: "unsubscribe &lt;password&gt;" in message body to
powerh-l-request at lists.sowder.com
http://lists.sowder.com/mailman/listinfo/powerh-l
This list is closed, thus to post to the list you must be a subscriber.
<< File: ALTERNATIVE.HTM >> 

CLB Littlejohn Frazer
Chartered Accountants
1 Park Place
Canary Wharf
London
E14 4HJ

Tel 020 7987 5030
Fax 020 7987 9707
www.clblf.com

The information contained in this communication is confidential and may
be legally privileged.  It is intended solely for the use of the
individual or entity to whom it is addressed and others authorised to
receive it.  If you are not the intended recipient you are hereby
notified that any disclosure, copying, distribution or taking of any
action in reliance on the contents of this information is strictly
prohibited and may be unlawful.

CLB Littlejohn Frazer reserves the right to monitor the content of any
message sent to or from clblf.com.

A list of partners may be inspected at the above address which is also
the address for serving documents.

CLB Littlejohn Frazer is registered to carry on audit work by the
Institute of Chartered Accountants in England & Wales, and authorised
and regulated by the Financial Services Authority for investment
business.

CLB Corporate Finance LLP is authorised and regulated by the Financial
Services Authority.


-- 
= = = = = = = = = = = = = = = = = = = = = = = = = = = =
Mailing list: powerh-l at lists.sowder.com
Subscribe: "subscribe" in message body to
powerh-l-request at lists.sowder.com
Unsubscribe: "unsubscribe &lt;password&gt;" in message body to
powerh-l-request at lists.sowder.com
http://lists.sowder.com/mailman/listinfo/powerh-l
This list is closed, thus to post to the list you must be a subscriber. 
  
       This message may contain privileged and/or confidential information.  If you have received this e-mail in error or are not the intended recipient, you may not use, copy, disseminate or distribute it; do not open any attachments, delete it immediately from your system and notify the sender promptly by e-mail that you have done so.  Thank you.