Hi Sergey

I guess I know the problem but am not sure.

>What did you correct in the table header to get it to work again?
The header file is simply an empty DBF renamed to HDR and in code I overwrite the bytes without touching the date-time bytes and then correcting the record counter manually.

The problem and maybe solution lies here:

I was locking the DBF by switching the first 2 byte, ie byte 1 becomes byte 2 and byte 2 becomes byte one so that novices can't open the dbf in foxpro and modify whatever they please.

When unlocking I use the dbf and if I can't use it I switch the bytes and try using it again and generally this was successful.

Now hat happens is that even if the dbf is locked the use command succeeds and the dbf is given for regular opening and when this dbf is opened all sorts of unknown problem crop up. These dbf's have memo fields, in fact almost all of the dbfs have memo fields in this app. Surprisingly, none of my other apps seems to be having this problem, just this my flagship products used by lots of people.

Right now I have stopped the locking and it looks okay. Also in such a dbf ie. locked but still usable running PACK on it seemd to solve this problem, does PACK change headers?

Thanks for responding and I couldn't respond earlier as I had my handsful with this problem.

Any suggestions.

>SWAG, maybe it has something to do with time difference between computers?
>
>>Hi All
>>
>>Maybe it is just me, but was there any issues with DBF headers on 1/1/2003. I had quite a few clients whose apps stopped working. In fact one client who uses my app since 1998 and has not required an update since then had his app stop working in 1/1/2003.
>>
>>In a case the problem was an Accounts Master which when GATHER MEMVAR MEMO would fail. In other case the screen for such DBF's would stop appearing though the system, the app and the keyboard are all working. Just noting would move.
>>
>>I had to correct the DBF header in all such cases and then the app would work normally.
>>
>>Any ideas was a header byte overflowing or such.