I'm creating a launch page in which the user will enter the customer number, and the report will bring back the invoices on that account. How can I code to allow my user to enter multiple accounts? There are to many accounts to use a listbox. Any suggestions? Thanks for your help.

How about a text box with commas in between the acount numbers?

Please update your profile signature with your product suite, release, and platform so that we can better help you.

That would be my suggestion as well.

Then you have two options:

The easiest would be just to use
WHERE ACCT_NUMBER IN (&ACCTS); The commmas should give you the correct syntax. However, if the values are alpha and quotes are needed you would have to do some additional work on the string.

The other option would be to test your parm string to see if it contains a comma. If so, branch to a piece of code that will test the length (which could tell you how many values were entered) and then use GETTOK to parse the string out into individual parameters which you can then use in WHERE ACCT_NUMBER EQ &VAL1 or &VAL2 or &VAL3, etc.;

I would also recommend using javascript to validate the input format.

Better to tell the user before executing the fex so that they can correct their input, than wait until the fex runs.

T

Or you can create a loop that asks you to enter a second (and more) acct_number. Each time you enter a new one it updates the internal amperfield by adding the new code to it.
Lot's of examples here on FP.

Think through the human factors. Since a report will (typically) silently skip over any erroneous account numbers, you may want to add a feedback-and-confirmation step:

In the launch page, use JS to check syntax on the entered text (as suggested above);

then proceed to a confirmation page (i.e. a report) showing what account numbers were parsed out and some looked-up database info (e.g. account name) so the user can visually validate the accounts; user should be able to revise, abandon, or confirm and proceed.

upon user confirmation, run the requested report.

Depends on business factors, but I would offer (and gently or firmly push for) that approach, rather than directly running with free-form input of multiple account numbers.