Bhavesh,

If you read many books on software development every one of them is going to say 1700 lines of code is an unmanageable amount of code for a method/function/procedure.

With what appears to be a heavy reliance on & macros VFP probably doesn't know exactly how big your modules are at compile time. Which means they probably won't break until runtime.

Just because VFP9 has removed some of the size restrictions I believe it's ill-advised to write code like that.

If you'd refactor your code into smaller components, eliminate & macros where there are better techniques like name substitution and these errors you are hitting will disappear.

> The method contains around 1700 lines of code. One thing I do not understand is that if vfp is not going to accept that many number of lines don't you think it would be better that it prevents me at compilation level just like we had it in vfp 6.
>
> Correct me if i am wrong. In vfp 9 they have removed this limitation or is it still there about 'program being too large'. the entire project contains around 700 screen files. Almost intermittently i face the above mentioned problems if this method exceeds the size mentioned in vfp 6.
>The moment I remove the number of lines it works and no error in the entire project.