Understood, Mike, Al, and Dragan, and I appreciate all your background of this, er, feature.

I'm just commenting that in 20 years of programming (since Fox/Dos) I've NEVER run into this, nor have I even seen the in clause in a replace statement in commercial software (accountmate, FoxMed, SBT, etc.). Of course, if I understand you correctly, this is a function of combining a SQL insert with a replace clause, which is something that I guess I typically don't do. I'm curious, if I had simply used APPEND BLANK, would this whole mess be avoided?

It's a bit like telling me I've been driving on the wrong side of the road all my life :-)

So far the clause does appear to be the fix, so I'm retrofitting all my code in the program immediately. Thanks again.



>Just to add to what Al is saying, never having needed something is a red herring. If you're not using the best way to do something, you are just lucky you were not bitten before.
>
>>Interesting - I have never needed that clause in the past (that I know of), but will definitely try it!
>>>>

>>>>PARAMETERS l_check
>>>>
>>>>* l_check values
>>>>* 1 = yes
>>>>* 2 = no
>>>>SET STEP ON
>>>>
>>>>thisform.pageframe1.page1.tol_no.Value = 0
>>>>thisform.pageframe1.page1.tol_yes.Value = 0
>>>>
>>>>
>>>>IF thisform.isloading AND thisform.isediting then
>>>>	l_check = VAL(jcpmt.tolerance)
>>>>ELSE
>>>>	replace jcpmt.tolerance WITH ALLTRIM(STR(l_check))
>>>>ENDIF
>>>>	
>>>>IF l_check = 1		&&yes
>>>>	thisform.pageframe1.page1.tol_yes.Value = 1
>>>>ELSE
>>>>	thisform.pageframe1.page1.tol_no.Value = 1
>>>>ENDIF
>>>>
>>>>thisform.pageframe1.page1.tol_yes.Refresh
>>>>thisform.pageframe1.page1.tol_no.Refresh
>>>>

>>>>
>>>>the replace command sometimes just doesn't update the table....what am I missing here?
>>>>
>>>>thanks in advance!
>>>
>>>Let's try with usual suspects first. In case you're sitting on an alias which is at eof(), the replace won't take place... unless
>>>
>>>

replace jcpmt.tolerance WITH ...whatever... in jcpmt

>>>
>>>which circumvents that.