Hi Charles,

I'm not a SQL guru either! BOb Archer is the SQL guru!

When I have a problem, he always tells me to run the Profiler. It will trace the commands and will show you where the failure occurs. When you know that, you can start looking at your views to make sure you have the correct field types, lengths, etc., etc.

I'm sure you know this, but the SQL Profiler is located under the tools menu in SQL Enterprise Manager. File | New | Trace | Connect to SQL Server | Trace Name | Run. Run your app until it fails. Then, you can look at your trace. It should show you exactly where the failure occurred.

Don't forget to cancel the trace.

My application is going pretty well.

Hope this helps,

TFISHER


>Hi Terry
>
>Well, I'm certainly at a loss when things don't go exactly right in SQL Server. Reminds me of my foxpro days about 15 years ago.
>
>How would I use the profiler to find out what is failing in the tableupdate ? I
>
>I think I may have this narrowed down to a problem with my sql numeric fields. In the sql designer my numeric fields show a length of 9 with a precision of 13 and a scale of 4
>In the VFP remote view, the fields have a length of 15 and decimals 4.
>
>I think there is a problem here because if don't mark the numeric fields as updatable I don't get the table update error ( though it still seems the records are not being saved to the sql table but that may be ... who knows.
>
>Obviously, I need to learn more about a more systemic way to figure out what is going wrong. Suggestions or further knowledge of the idiosycracies of numeric fields between sql and vfp would be appreciated.
>
>How's your app these days?
>
>
>>Hi Charles,
>>
>>Have you tried using SQL Profiler to trace what is going on?
>>
>>Hope this helps. You certainly helped me enough!
>>
>>TFISHER
>>
>>>Using remote view in VFP 8.0
>>>
>>>Tableupdate fails with the error 1585 'Update Conflict'
>>>
>>>Anything in particular I should be looking for in trying to troubleshoot this?
>>>PK is a guid(36) with a uniqueidentifier on the back end and is being properly generated on the front end. All fields except pk allow nulls.
>>>The one logical field in VFP is mapped to a bit field in sql. Text fields are all mapped to nvarchar. two datetime fields.
>>>
>>>Is there a way to tell which field is causing the error?
>>>
>>>Obviously floundering around here. Any guidance appreciated.
>>>
>>>TIA