RE: Update Conflict

Hi Lee,

Thanks for the links. I'm hitting the issue described in 253886. I don't
quite understand the workaround.

Create a stored procedure that returns the data stored in SQL Server in a
converted format with millisecond precision removed. For
example:(convert(datetime,convert(char,getdate())))

How does this work with remote view? Does it mean that the remote view will
call this stored procedure?But how?

Thanks,

Peter





"Lee Mitchell" wrote:

Hi Peter:

I don't know what might be causing this. However, I am sending you several
articles that mention this error in hopes that they may shed some light on
this problem.


253886 An ODBC error may occur when you update the DateTime data in
Microsoft SQL Server 7.0 or later versions and in Visual FoxPro
http://support.microsoft.com/default.aspx?scid=kb;EN-US;253886
148999 BUG: ON ERROR Not Called When Update Conflict Occurs in Grid
http://support.microsoft.com/default.aspx?scid=kb;EN-US;148999
177062 PRB: Update Conflict When Key Field Is Not Unique in Remote View
http://support.microsoft.com/default.aspx?scid=kb;EN-US;177062
138809 PRB: Update Conflict w/Remote View When WhereType Set to Time
http://support.microsoft.com/default.aspx?scid=kb;EN-US;138809
198606 "Update Conflict" message when modifying SQL Server data
http://support.microsoft.com/default.aspx?scid=kb;EN-US;198606

I hope this helps.

This posting is provided "AS IS" with no warranties, and confers no rights.

Sincerely,
Microsoft FoxPro Technical Support
Lee Mitchell

*-- VFP9 HAS ARRIVED!! --*
Read about all the new features of VFP9 here:
http://msdn.microsoft.com/vfoxpro/

*--Purchase VFP 9.0 here:
http://www.microsoft.com/PRODUCTS/info/product.aspx?view=22&pcid=54787e64-52
69-4500-8bf2-3f06689f4ab3&type=ovr

Keep an eye on the product lifecycle for Visual FoxPro here:
http://support.microsoft.com/gp/lifeselectindex
- VFP5 Mainstream Support retired June 30th, 2003
- VFP6 Mainstream Support retired Sept. 30th, 2003


Hi,

I'm getting a update conflict in VFP8 SP1 when I update one particular
field
of a record in a particular SQL SERVER 2000 table thru remote view.

1. I'm sure that no one is updating that record.
2. I have traced in both VFP and SQL Server Profiler and don't see any
updating before my update.
3. It does not happen to every record. For example, if I duplicate a
record (except the primary key) which has the update conflict issue, the
new
record does not get update conflict.

The SQL Server is running on Compaq Proliant with Raid (probably Raid 5).

Can it be caused by hardware?






.

Relevant Pages

  • RE: Update Conflict
    ... Microsoft SQL Server 7.0 or later versions and in Visual FoxPro ... record which has the update conflict issue, ...
    (microsoft.public.fox.helpwanted)
  • RE: Sharepoint issue
    ... do you mean Microsoft SQL Server ... 833183 You receive a "Cannot connect to the configuration database" error ... This newsgroup only focuses on SBS technical issues. ...
    (microsoft.public.windows.server.sbs)
  • CERT Advisory CA-2002-22 Multiple Vulnerabilities in Microsoft SQL Server
    ... The Microsoft SQL Server contains several serious vulnerabilities that ... These vulnerabilities are public and have ... the same privileges as the operating system. ... a compromised Microsoft SQL Server can be used to take ...
    (Cert)
  • [NT] FoxPro ODBC Driver Buffer Overflow via SQL OpenDataSource()
    ... OpenDataSource function in Microsoft SQL Server when we are connecting to ... "Microsoft Visual FoxPro Driver". ... we can overwrite EIP register with any value. ... SELECT * FROM OpenDataSource('MSDASQL','Driver=Microsoft Visual FoxPro ...
    (Securiteam)
  • RE: Update Windows XP Home SP2
    ... I have tried many times unsucessfully to install the Microsoft SQL Server ... Download Center. ...
    (microsoft.public.windowsupdate)