General information
Category:
Coding, syntax & commands
Title:
Dirty Buffers Error 1585
I have an illusive problem that pops up about once a day. It's the 1585 error. The trouble is, the error comes up when adding a record and values in curval and oldval do not evalute, because no record exists (recno is -1). I have a VB programmer here that is writing to the same table that I'm getting 1585 on. I have finally been able to reporduce the error by having Fox sitting on the record when ADO updates the memo field. Then try to save an added record(Note: added while sitting on record updated by ADO) in Fox and I get 1585. On local testing I can say overwrte changes and that works(even though there is no real change to overwrite, rembember, its a new record). In live enviornment user cannot force update. I cannot get them to turn off this ADO VB $#&%$* so that I can verify it's the true problem. Seeing it happen in the test env doesn't seem to be enough. I have to hear it's a Fox problem. I think the third party data consumer needs to go.
Any advise on why Fox might be seeing this as a 1585 ditry buffer is greaty appreciated.
Much Thanks
Jeff
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only