>>>Hi everybody,
>>>
>>>The more I work with this form, the more it misbehaves. Here is one little puzzler - see attached.
>>>
>>>I add a new row in the grid. Since a few of my fields are integer, the 0 is inserted in these fields.
>>>
>>>Ok, I'll start entering info and tabbing to the next grid cell. As soon as I'm about to tab into Seats # cell I have that weird behavior - the cell is PARTIALLY highlighted. In the grid's Init I set all textboxes format to be KF.
>>>
>>>What is going on, why it's only this particular cell and what can I do to fix it? The problem with partial highlight is that 0 gets appended to whatever I type.
>>>
>>>Thanks in advance.
>>
>>Have you tried not to set format to KF for the "offending" cell? Does it make a difference?
>
>I think I actually just solved it. I added setting the K format in the code that sets this page for the column. I'm going to add K! format to the Row column now.
>
>The 2072 error is not appearing right now. I added this code
>

>local loError as exception
>select rsTSBlocks
>
>try
>
>	INSERT INTO rsTSBlocks (TemplateID) VALUES (thisform.oCurrentNode.values('TemplateID').value)
>	GOTO RECNO('rsTSBlocks')
>*!*		append blank
>*!*		replace TemplateID with thisform.oCurrentNode.values('TemplateID').value in rsTSBlocks 
>	this.parent.grdSeatBlocks.refresh()
>*	this.parent.grdSeatBlocks.colLevels.cboLevels.listindex = 1
>	thisform.VenuesTree.enabled = .f.
>	this.parent.grdSeatBlocks.setfocus()
>catch to loError
>	if loError.errorno  = 2072 && obscure VFP bug - try the same code again
>		oAppObj.write_log('Error 2072 detected ' + loError.message, program(), 'E')	
>		=MESSAGEBOX('The error 2072 is the internal VFP bug! Please try closing the form and re-open!',48,'Internal VFP Error')
>	endif
>endtry
>

>
>I really can not do anything with it. I deleted all records for that particular template and the error is no longer occurring yet. However, I was getting it in other places, such as Delete block button. It is extremely frustrating - I spent the whole day on this form and on one particular page of that form.

It never ever happens to me. My code usually works immediately and flawlessly ..............................NO <g>.

Sorry for your frustration.