>>>>>
>>>>>Connectivity error: [Microsoft][ODBC Visual FoxPro Driver]Field iCust_id does not accept null values.
>>>>>
>>>>
>>>>The first suggestion is to remove Psnldets.icust_id from field list, just because it's redundant (you have Customer.icust_id already). Another question is about your setting. The error message indicates that you use Remote View again VFP data. Is it right? Could you use Local view?
>>>
>>>Yes I am using a remote view. There are two reasons for this. One is that within my applicaiton, the users will be dealing with multiple clients. Each client needs a completely separate database as they each have their own batch of customers / orders etc. I thought that I could create one connection in the local DBC with all the views based on that connection, and when the user needs to switch to a different client, I could just change the Data Source Path for my ODBC datasource to point to the appropriate database and then all my views would automatically point to the right place.
>>>
>>>The second is that the first version of my app will actually be deployed with a Visual Fox back end, upgrading to SQL Server in a later implementation. Views seem to be really slow when using a Fox back end so I thought that it would be best to use remote views so that I can utilise techniques such as progressive fetching in order to speed up the response of the interface.
>>>
>>>Do you think that this route is an poor choice given the scenario?
>>
>>It can be justified if you really move back-end to SQL-Server. In other case Local View is faster then Remote just because you eliminate ODBC-layer. C/S system assumes different methodology, i.e. doing traditional system you are prompted to open all data at once and this is the fastest way, in C/S you should retrieve small recordsets (as small as possible) to get appropriate speed.
>
>I have removed the duplicate iCust_id and tried the same process. I still get the error described aboved. I then tried creating a view based solely on the customer table and tried the same process, but once again I get the same error.
>
>Any Ideas?

I have just created a simple table and accessed it via ODBC and a remote view - it worked fine! - How have you set the remote view up and how are you adding records? (Insert, Browse etc)

There must be a solution!!

Ian