Yes. It's 'KeyFieldList','UpdatableFieldList' property. However, if you don't have much experience using remote views, then start with View Designer. Moreover, it should be specific reasons (usually complicated SQL) not to use it.
>I see. I'm new to this view stuff. So I take it I can set the Udate Key Field and Update Fields through this also?
>
>>Select MyView
>>=CURSORSETPROP("SendUpdates",.T.)
>>
>>
>>>That was the problem, I didn't have the Send SQL Update fields checked. But how do I do this programatically without using the view designer. I see no options in CREATE SQL VIEW.
>>>
>>>>I mean 'Send SQL Updates' box, or 'SendUpdates' property.
>>>>
>>>>>In the Update Criteria tab of the view designer it is set to SQL Update.
>>>>>I assume this is default if I used the CREATE VIEW COMMAND and not the View Designer?
>>>>>
>>>>>>Is your view updatable?
>>>>>>
>>>>>>>When I have the view open in the current work aread and I do this:
>>>>>>>lSuccess=CURSORSETPROP("Buffering", 0) I get "Property out of bounds."
>>>>>>>
>>>>>>>If I make a change in the browse window and then do TABLEUPDATE(2,.T.) the change appears in the browse. But if I close it and browse again the change is gone. ??
>>>>>>>
>>>>>>>
>>>>>>>>Make sure that there is no buffering with=CURSORSETPROP("Buffering",0) -or-
>>>>>>>>make sure you issue a TABLEUPDATE(2,.T.) before closing the table.
>>>>>>>>
>>>>>>>>>
>>>>>>>>>OPEN DATA dbc
>>>>>>>>>CREATE SQL VIEW TWCView;
>>>>>>>>> CONNECTION TWCustomers SHARE;
>>>>>>>>> AS SELECT * FROM access.customer
>>>>>>>>>
>>>>>>>>>I make changes but they are only saved to the local temp table, not to the actual connected Access database? I thought you could write to the file to?
>>>>>>>>>
>>>>>>>>>>Kevin ---
>>>>>>>>>>
>>>>>>>>>>Well...Not many, really, if you're just appending records.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>Ok, great, just got an ODBC view into an Access database. I have heard that performance with ODBC is pretty bad. If I am just appending records to an ODBC database once a night, I take it performance isn't really an issue. What database functions are hindered with ODBC.
>>>>>>>>>>>
>>>>>>>>>>>>It can read/write them as remote views via ODBC. There is no native use of Access databases.
>>>>>>>>>>>>
>>>>>>>>>>>>>Does VFP 6.0 import and export to Access databases? Or even better, will it write and read directly to an Access database?
Edward Pikman
Independent Consultant