Thanks Josh. I would not have thought about creating a temp dbc. I'll try that.

>You can create a remote view in code. Use the CREATE SQL VIEW command. It does mean that you'll be adding and deleting views from a dbc each time you create or remove a view. I usually create a temp dbc for each user at startup.
>
>Another way to deal with this is to create cursors and leave them read only. When the user needs to modify a records, bring that over in a view parameterized on the primary key of the table. This way you can use views to handle updating data and SQL pass-through for running your queries. This method has always worked well for me.
>
>>If, instead of using a remote view definition in a .dbc, you create a cursor and try to use CursorSetProp to make it work like a view, you cannot requery() the view. What am I missing here? Why would you want to make an updateable cursor if you cannot requery it (especially if it's a paramaterized view)?
>>
>>I realize that instead of requery() I could just create a whole nother cursor, but it seems to me that views and requery() were meant for each other and in some situations it might be helpful to cretae a remote view in code.