>>>But since it's not going to affect anything but file-server apps (like VFP, Access and maybe a few more), I guess it will not be fixed.
>>
>>The dilemma is that I'm not sure what to ask for:
>>- disable write cache on all WS - it seems that everybody agrees that would be a good thing, but it is very difficult to implement for 300 WS in continuous change/"upgrade"
>>- disable write cache on the server - everybody seems reluctant to do this, including myself, and yet I suspect that the problem is with the server cache.
>>- not use autoinc at all.
>>- ask God to help us - you don't need to comment on this one.
>
>I won't comment on #1 and #4 because I think they are unrelated to the matter at hand. IIRC, Jim Nelson was the first one here to investigate the matter at length, years ago, and (IIRC again) he said that #2 solved the matter for him. Now this may be made obsolete - it was on W2K servers then - but maybe not. If I said "I guess it will not be fixed" the same may have been true then, i.e. wasn't fixed since, because Word manages to save a file almost every time, therefore everything must be peachy.
>
>#3 is always a solution. Use a GUID, use a WSID+sys(2015), roll your own, anything but. I haven't found any use for autoinc, because by the time it appeared, my newid.prg (and anybody else's as well) was bug free.

We do have our key generator, autoinc was more an experiment, at least for me - it felt like getting something for free...