Thanks!!!
this will solve the problem
for detail refer VFP9 help
SharathMum wrote:
SET TABLEVALIDATE TO 0 (zero) this will solve the problem
for detail refer VFP9 help
SET TABLE VALIDATE TO 0 does not "solve" the problem. All it does is mask it. VFP 9.0 is does stricter checkings and finds things that were wrong but not caught by the parser before.
Even though it gets you going for the moment, it does not fix the problem, just hides it. You should still see what's wrong and fix it in the table itself.
SharathMum wrote:
SET TABLEVALIDATE TO 0 (zero) this will solve the problem
for detail refer VFP9 help
SET TABLE VALIDATE TO 0 does not "solve" the problem. All it does is mask it. VFP 9.0 is does stricter checkings and finds things that were wrong but not caught by the parser before.
Even though it gets you going for the moment, it does not fix the problem, just hides it. You should still see what's wrong and fix it in the table itself.
i agree with u,
its my mistake i should have post the warning also that its a temporary solution
Tool to Repair
CM Table Repair Utility http://www.universalthread.com/wconnect/wc.dll?2,54,1,5
http://ckkiet.blogspot.com/2004/07/one-of-possible-cause-vfp-table.html
