>>I wasn't trying to imply that the Mover doesn't need to work if there aren't any records in the full list. It should. I was just stating that I haven't had that experience.>
>
>I'm guessing no one has yet. Add that to the fact that mover objects aren't the most popular components anyways.
>
>>By placing a filter in the PostInitHook of the Data Environment, I wasn't talking about adding a view parameter there. If you are trying to filter your records via a view parameter, don't. You will have to requery your data all of the time. I would use a view that gives you the entire set of records, and then filter those records using the SET FILTER command. You can place this filter in the PostInitHook of your full lists data environment.>
>
>
>Ah, I see you idea. Sounds like a good alternative.
>However, if a user is allowed to dynamically change what shows up in the FullList (my specific example is a combobox of products, and then only customers that have that product show up in the FullList).
>(wow, my sentences are long)
>Anyway, if a user dynamically changes what shows up in the FullList, then it would HAVE to be requeried each time, right? I'm guessing that if I SET FILTER in the PostInitHook of the D.E. then that filter would only work once, since PostInitHook only gets called once. Is that a correct assumption?
>
>Still learning,
>Dustin

This is correct that it will only get called once, but that is all is needed. Once the filter is set in that work area.... it stays. I created a mover about 3 weeks ago that was doing almost the same thing... and it works great.