My explanation wasn't complete. The first time FoxPro generates the error it still removes CDX reference. You can catch error 1707 and open table again.

>

TRY 
	USE mytable
CATCH TO oExp WHEN oExp.ErrorNo = 1707
	USE mytable
ENDTRY

>You are right.. its silently removed... and second time open without problem..
>When it so.. is it possible to make same silent CDX remove in runtime to supress an error?
>