Again no big deal, but they could have told us. Even back in the IBM days, and they were not examples of programmer friendliness either, you got an exhaustive list of everything that they knew changed. You would wait for the next release anyway for those that they did not know. Ok, but that was before.

Now they changed AFIELD, ok, that is documented. But in vfp 3 when you CREATEd a CURSOR from such an array, it did not inherited the DBC bullshit (triggers, chmiggers and other RIggers). Now they do, so you have to blank out elements 7 to 16 before you issue the CREATE CURSOR statement.

Again no big deal, but a pain, because what used to run in VFP3 won't run in VFP5, and you cannot have common sources, making the transition more abrupt.

    *----------------------
    procedure Clone(yClone)
    LOCAL aStruc(1),n,n1,nEl
	if parameters()=0
		yClone= this.cClone
	endif
    =afields(aStruc,This.Alias)
	* vfp5 patch nr 1
	nEl= alen(aStruc,1)
	for n=1 to nEl
		for n1= 7 to 16
			aStruc(n,n1)= ''
		endfor
	endfor
        * end vfp5 patch    
    create cursor (yCLone) from array aStruc
    select (yClone)
    this.nClone= select()