Hi Linda,

>This is interesting because it implies that using OOP is more inefficient in terms of memory management than the old fashioned procedure files...If I create a custom object to store methods, it's really more inefficient than simply creating a procedure file and issuing a SET PROC TO...?! Unless SET PROC TO also loaded the whole proc file into memory, which doesn't seem logical, considering the limited memory of the older machines. Hmmm.

OOP is more flexible and therefore makes in most cases less efficient use of resources, yes. OTOH, OOP is more efficient in the design of applications and therefore results in faster and more stable applications.

BUT, Windows and VFP are written in an OOP language. Furthermore, VFP is an interpreted language. The difference between an object and a procedure might exist in terms of memory usage, etc. but it should make little difference compared to VFP and Windows. For example, creating a form class allocates memory for the bitmap of the form, which can be several MB on a contemporary system with true color and a high resolution.

If memory is such an issue, I'd either search for alternatives like pooling objects if the number of hits are the issue, or choosing a different language like VB, VC++ or maybe C#.

Christof