Thanks, Craig. So I can't do what I want with remote views. Will it work with local views, which shouldn't involve the ODBC driver?


>Technically, you can't do a VFP back end have a C/S application as processing still occurs on the workstation. In a true C/S application, there is database processing that occurs on the server. This won't happen with VFP.
>
>The VFP ODBC driver doesn't support calling stored procedures for default values, which is what I assume you are doing.
>
>
>>I'm setting up my first C/S app that has VFP (7) on both the front and back ends, and running into a problem when trying to add a record to the remote view, to pass back to the actual table.
>>The problem is that the table won't accept null values in the primary key, so the TABLEUPDATE is returning false.
>>Of course, that's not the problem - it's just the symptom. The actual problem (as I see it) is that the DEFAULT values of the fields (including the PK) in the back-end data don't get populated when I add a record to the remote view.
>>So how do I get around this? The view is defined properly, I believe - all updates are sent from the view, and the DEFAULT values work properly when I work on the back-end table directly.
>>The most obvious part of this problem affects the PK field (in each table), but it will also affect the default values in other fields.
>>TIA,
>>Mark