Hi Andy,

Thanks for responding, we are just in the process of prototypeing for our migration to SQL and are coming up with items that we didn't suspect would be issues. The "Ad Hoc" queries being one.

We ruled out using views because we'd have to create multiple views for each of the tables (150) and doing a view on the fly seems like it would bloat the dbc and create other issues to be worked around as well - like naming conventions to prevent contention. So we attempted to use sqlexec and manipulate the cursor into an updatable entity using cursorsetprop - unfortunately without success at this point. Specifically we are getting a message "No update tables are specified. Use the Tables property of the cursor (Error 1491)"

SQLEXEC(oapp.nconnecthandle,"SELECT Um.UM, Um.[DESC], Um.NODECIMALS FROM dbo.UM um","Um")

*CursorSetProp("SendUpdates",.T.,"um")
CursorSetProp("BatchUpdateCount",1,"um")
CursorSetProp("CompareMemo",.T.,"um")
CursorSetProp("FetchAsNeeded",.F.,"um")
CursorSetProp("FetchMemo",.T.,"um")
CursorSetProp("FetchSize",-1,"um")
CursorSetProp("MaxRecords",-1,"um")
CursorSetProp("Prepared",.F.,"um")
CursorSetProp("AllowSimultaneousFetch",.F.,"um")
CursorSetProp("UpdateType",1,"um")
CursorSetProp("UseMemoSize",255,"um")
CursorSetProp("Tables","dbo.UM","um")
CursorSetProp("WhereType",1,"um")
CursorSetProp("Updatablefieldlist","um,desc,nodecimals","um")

Do you have any thoughts on the cursorsetprop values? Should we be looking at using cursor adapters?