The reason I am asking was I am building an in-process .DLL for running inside MTS and IIS. Once the server starts getting called heavily, the only way to update the business-logic method code would be to down the whole web server. So I figured that if I just had all the methods in memofields, then I could open the table from VFP at any time to update the code. There would be a point in time (seconds?) where people might be running an old method, that would be acceptable to me if it meant the server was always available.

Slower than mollases?


>Ok, you are talking about a different application for the "Code" table than Steve. It makes alot of sense for you to do it this way. For just plain method code, though? It doesn't make sense. Where you have many possible procedures that you need to cross reference against a value like you, I'd do it.