I see what you're getting at now Linda.

And I surely don't know the correct answer.

Speculating, though... assuming that a Custom class would be loaded only once (at least the one with all those common procedures), I would *guess* that it comes out almost the same. Also guessing that a PROC file stays loaded throughout.

IF VFP ever gets to the point that we can generate "reentrant" executables (and by 'reentrant' I mean the old mainframe term that a program does NOT self-modify any part of itself and so can be executed by many processes at the same time) then maybe the OS could have other options.

JimN

>Thanks for jumping in...the more the merrier!
>
>I was referring to a procedure file. In my way of thinking, there are two ways to set up a large body of generic procedures for use in an application: (1) you can put a lot of functions in a procedure file and issue a SET PROC TO or (2) you can create a custom class with the same functions. What I am trying to determine is figure out which way is more efficient in terms of memory management...which is a big issue in web applications, since each time a user makes a hit, you have to reload all the environment, global variables, objects, etc. back into memory to deliver one web page. Then everything is lost until the next hit, when it is all reloaded again.
>
>There are probably other ways too, for example, creating a library. Perhaps I should move this thread over to the COM or web area to get some more ideas from that direction...
>
>Linda