A mature VFP7 project of mine has suddenly stopped compiling. No files
added or deleted, just a couple of cosmetic changes -- but VFP7 won't
compile the project. No error message, VFP just freezes during compile.

Other VFP7 projects seem to compile OK. Nonetheless, I reinstalled
VFP7, but that made no difference.

Any suggestions?

Thanks --
Doug Schwarz

Doug,
This is almost always due to a "corrupted" form, classlib or report. Watch the messages as the build happens and note what component is last displayed. Then after you've started VFP again, try recompiling that file separately with COMPILE FORM ... , COMPILE CLASSLIB ... or COMPILE REPORT .... Now try the build again. If it once again "hangs", then it's probably the next item in the project. Because that isn't always what you think it is, you'll need to open the project as a table, locate the last "good" one and manually compile the next one in the project. An alternative is to save off the "only" files you changed, restore everything else back to the last good build, and then only replace the new files.

Rick

"Doug Schwarz" <odougs (AT) alum (DOT) colby.edu> wrote

Thanks. Recompiling individual components didn't seem to help, but I
did have a good backup I could work from (thank heaven!), and everything
seems to be OK now.

-- Doug

Rick Bean wrote:

"Rick Bean" <rgbean (AT) NOSPAMmelange-inc (DOT) com> [WA] wrote:

i.e. a memo corruption??

Seems to be a weakness of the VFP model. Doesn't make much difference to me
because I only use memos for data.

Are classes implemented via memo fields?

regards - anthony shipley

look, ma - no .sig

Anthony,
Yes, virtually all VFP project components use tables with memo fields - including Projects!

ClassLibs, Forms, Reports, Labels Menus, Projects and Databases all have a "memo" file.

Rick

"Anthony Shipley" <astechsystems (AT) iinet (DOT) net.au> wrote