>>The SQL window doesn't reverse engineer the code so changes there won't be saved. However, what I'd do is copy the code from there, fix it and save it in a PRG, and run the PRG to create the view.
>
>I've had this same problem and have been working around it the same way you are. Is this a foxpro bug or is there something else to this I'm missing?

I haven't actually had this problem. However, I always save my views in PRG files. If anything's messed up in a view you can't open it in the View Designer and you're stuck, unless you've saved the view in code or have run GenDBC and saved the PRG it creates.