>You have not asked a simple question:-).
>While I am only tryng to get the primary user group online ASAP, eventually I will have 22 user groups. Four will depend on one field for the primary WHERE ( forcetype = 1, =2, <3 =3) The rest will need either unit = or section = . (note, these are keys, not text fields) Besides these default group level 'filters' (which may be done on the server) the users need to limit from a single person by sernum or a foriegn key to another application(PeopleSoft) to a single occupation code, a single rank, electoral district, religion, marital status, or several other possible fields and combinations thereof. Some may be done simply as reports for information(i.e. electoral district or religion), but rank, occupation code, and in some cases as with large units, sections as well as units. In the case of the first four groups above (specialised personell offices) any combination of unit/section/rank/occupation may be needed. Unfortunatly, the only predifined parameter for the primary group is
>forcetype<3 ( Military personell only), the remainder of the desired WHERE s need to be determined at runtime. It is most likely that sernum or psid will be the most used parameters.

How are you dealing tiwh <3 in the parameterized view? What would be the force type of those others. I'm beginning to see the complexity of the view required. You might need to use multiple views each with different paramaterized views. Then in the load open one or the other view, but using the same alias name for both. Then bind your your objects to the alias.