>Silvio, I appreciate the input but recreating the where clause isnt the problem. Implementing it in an existing view is the problem and w/o macro substitution, I don't know how you can. I'll just find another way to deal with it.
>
>Thanks again.

I haven't tried this, but here's an idea:

- Create your updatable view assuming you know the primary key (ie WHERE PrimaryKey=="SOMETHING")

- Create your SQL statement on the fly, like you currently do, but just return the primary key[s] found. Then, with those primary keys, you can use the updatable view created above.

This way, you have a single updatable view (without macro substitution), and the query you create on the fly is only an intermediate. As for speed, chances are you have an index on that primary key, so Rushmore will kick in!

Hope I'm clear enough...

Sylvain Demers