Hi - after a lot of observation but little formal testing, It seems to me that the following is true in the case of (at least) VCX forms.

1 - VFP seems to be able to automatically handle "vcx bloat" for forms as long as the forms are under a certain level of complexity (or perhaps number or type of controls). Most of my simpler to intermediate complexity form VCXs rarely need packing. Somehow VFP is dealing with it itself.

2 - At some point - where the form reaches a certain level of complexity, number of controls, or some other set of circumstances, all of a sudden vcx bloat becomes a major issue. I have certain forms - that I can literally go into and do nothing more than move a button up a pixel, change one line of method code, or any other change - no matter how minor - and when I save - all of a sudden I have several hundred deleted lines in the VCX. If I go in and work with my class for awhile - saving on a regular basis - very quickly my 250 row VCX hits several thousand rows and I end up packing after every set of saves to keep it down.

question - can anyone comment on the above and specifically, comment as to what set of circumstances suddenly kicks off this VCX bloat?

Thanks!