Problem using datetime() as key value in sqlserver

[canter]

I have a little view set up that does nothing but update a particular SQL record on my backend database. The problem seems to be that I'm forced to use the date/time the record was entered into the system as my keyfield for this database. (its the only thing guaranteed unique in the record). If I change the keyfield to something else (say, the order number), the update goes through. When I use the date/time field as the key, I get an "update conflict" message. Is there a problem between Foxpro's datetime format and the one used by sql server 6? I can't seem to find this problem addressed ANYWHERE!

Thanks in advance,

Duane Lunday

 

[foxdev]

On your properties for the remote view there should be a set of radio buttons to set the Update Method, with choices such as "Key and Modified" and "TimeStamp". You might try adjusting these to see if it helps. Robert Bradley

http://www.foxdev.com/

Got extra money lying around? Visit:

http://www.agrainofhope.org

 

[fluteplr]

I would seriously try to get whoever designed the sql server table to add a valid primary key (add an integer identity field if nothing else seems appropriate). Using the datetime of an entry is a disaster waiting to happen.

 

[canter]

Thanks for the replies. It seems that changing the field's type from date to text fixed the problem. As far as it being a disaster waiting to happen, welcome to my career!