>>>You have notified Fernando so he can fix this?
>>>
>>>The behaviour is, that VFP simply deletes the old record while safing the class and appends new records to the VCX. So VFP makes shure to get the last - valid - record. For example it does not care about SET DELETED. In older versions of VFP the deleted records in the VCX where never packed.
>>
>>Hi Lutz,
>>
>>I did copy Fernando on that last message, but I will bring it to his attention again.
>>
>>I thought of it as *my* problem rather than in Fernando's, but I guess in a way it can be dealt with by foxbin2prg.
>>
>>Thanks for the suggestion,
>>
>>Alex
>
>FoxBin2prg should, under no circumstance, destroy a binary. So it must deal in the expected way, iow with the bottommost recordset of 2 classes with the same name.
>
>We never know what strange setting we might run into.


Hi:

I may add this autofix, but I'm not 100% sure that the good record will be *allways* the one with the bigger Timestamp.

If I add this autofix, I could add a switch to disable it, just in case someone do not want it, but the problem here is FoxBin2Prg taking a decision by it's own.

Another possibility is to ask the user if want to autofix. That may be a better approach...


What do you think