Dragan,

> OK, I've done some more tests - and AGAIN uses the same
> recordset. Without it, it opens a separate recordset
> (this sounds logical) but you either have to use a
> different alias or a different datasession. Of course,
> the parameters (if it's a p-view) should be fairly local
> to the procedures which open and requery them, otherwise
> we're into trouble requerying - I'm not sure if
> requerying one of them does (or doesn't) requery the other.
> I've tried it (without the Again), and nothing bad
> happened as long as I put the alias of the view in the
> Requery("alias") - it requeried only that one and didn't
> touch the other.

Yeah, with the AGAIN, a requery appears to affect both, without the AGAIN, it is two separate instances. It makes sense that the ALIAS keyword is required when AGAIN is not used (well, and even if it is), since Fox can't have two work areas of the same name (in the same data session).

> This is actually nice. You may have, say, case histories
> for two parties in the two instances of the same view,
> from the same table, at once.

Exactly...that was why I was so frustrated when it wasn't working, since two instances of the same view seemed so elegant for the copy operation...I was making it way harder than it was!

> Thank you for inspiring me to make things clear for myself :).
> I'd never dig into this without your puzzle.

Hey, if it's puzzles you need, just keep watching for my threads...I am the master of them...both real and ones like this that come up because of my silly mistakes!

>>Joe Kaufman

>And this is another puzzle - UT says I'm answering to Terry Miller...

We are all from ENCOMPASS Health Mgmt. Systems, and Terry registered this account, so...there will be some other names posting on this account before we are finished with our application, I assure you!

Thanks for everything!

Joe Kaufman