My experience in cleaning up the code of others and making an application reliable is that reserved words should never be used. I have seen applications in VFP and VB run for months and then fail for no known reason. Upon examination of the code I resolve the issue or issues and then the application will once again run.

Aside from the use of reserved words you could have other issues.

>In this case the variables do need to be public but I don't think that's the problem. You might be onto something with the array name.
>
>I've been aware since I first looked at the application--before I even committed to support it--that there are reserved words used as variable and array names. This one is called "case". As I mentioned, the original code was written by a teenager about 15 years ago; it was his first program. Even though the reserved words raise red flags for me, the client says they have not had problems until recently. Were reserved words less of an issue in VFP 5? What kind of errors DO they cause? Why does it occur immediately following my new code? Obviously, I haven't had any personal experience--not that I'd expect you would either <g>--but perhaps you've at least read of it here.