>Terence,
>
>According to the documentation, datasessions are only related to forms, formsets and toolbars. I didn't think you could mix datasessions on a single form.
>
>Any other ideas?
>
>TIA
>
>Rex
>

Um.. if in same form, as you said use different alias and close the alias after switch pages.
I get similar problem in my application.

There are a PRO_INV_NO (Pro-forma Invoice #) and also INV_NO (Invoice #) as index in ORDERS table.

Because there will be a different timing on product out.
This is possible for some later Pro-forma give fast finish and take the early INV_NO or
some Pro-Forma can't make final confirm and thus rejected.

Therefore, when user need to fill in INVOICE info,
I need to make a view for search the current last INV_NO for reference.
(or auto-add next code.)

This may give side effect if I change the original alias ORDERS index by INV_NO..
One of the side effect is DROP the correct relationship between ORDITEMS
The grid will show a unwanted data, full or empty. ;(

What you need to take care is to adding code to:
Select CorrectAlias on each code to prevent wrong alias select and
do serious data changing by code.
Then, try to close the view alias after use if not needed.


>>Well, the view data requery always to make it up-to-date.
>>Otherwise, users will confuse that the data filled in application or not.
>>
>>Generally, you can open same table or view more than one time in different alias in shared.
>>For example, create a sales order, open the ORDERS table again
>>to check if the ORDER_ID is filled by other sales.
>>
>>The extra alias is to avoid the original alias jump record which fire auto-update on ROW BUFFER MODE
>>
>>Of cos, other sales may added the new record already in other machine,
>>you must requery or re-open the alias to ensure refresh the up-to-date data from server.