Here's another way which is also not very clean, but might get you where you
want to go.  It assumes that only one view will be open by any given user at
a time, so it's limiting in that sense, though you *might* be able to work
around that by adding a date field and always querying the most recent
date...but I'll keep it simple for the time being.

Create a table with two fields, UserID (with a default value of user_name()
or suser_sname() or whatever you prefer) and SQLText.  Store your ad-hoc SQL
code for each user in the SQLText field.  Then use OpenStoredProcedure to
execute a parameter-less SP which opens the table, looks up the SQLText for
the user who's calling the SP, then execute the code found in the associated
row.

Along the same lines, you can also create views in your database that get
saved under the user's name instead of dbo (i.e., mydb.rmorley.tmpview), but
that requires granting permissions to create views in general (which is
usually not desirable), and can be awkward to access from an ADP...the
table-based approach is probably easier.

Rob