>stephen,
>in each page of the pagefram , i put:
>select alias1, and conversely, select alias2, for the 2nd page, it does switch the work area. i know this because i simply put a command button on page1 and put skip to move the record pointer.
>
>the problem is the wizbtn (txtbtns - top/bottom/next/prev/ etc.) does not work, it seems like it defaults to the first workarea. help.
>thanks
>frank

Never trust a Wizard. Micky Mouse found this out in Fantaisa <grin>

So you could subclass the buttons that are there now, or make your own that just go next, previous.

Just a question how the data is getting populated for your form. Where is it done, or is that done via another wizard? Maybe the data environment?

When you say cursor I wonder why you are not using views?

to make one just add this to the start of your seelct statement:

CREATE SQL VIEW "lv_invoice_sum" as ;
;
SELECT Armast01.custno, Armast01.cshipno, left(artran01.item,2), ;
armast01.invno,....

In the end of that SQL take out the INTO cursor, or array, table etc.

Now you can do this:
Open data My_DBC
use lv_invoice_sum in 0 nodata
index on custno + cshipno tag custship
requery()

This will load a structure of your data, allow you to have an index on it, then fetch the data into an pre-indexed environment.

faster then using Order by in your querys!

__Stephen