>Hi again Phillip ---
>
>I'm glad you're seeing the light :-)

Heh, if I didn't see the light, what kinda programmer would I be, eh? ;)

>Now, one more thing: You shouldn't have to worry too much about dynamic data...just have a tier property called ObjectsCount that has total object count, CurrentObject which has an index value (num), and GetNextObject which sends info to instantiate the next object in the presentation tier.

Well, the issue that I'm thinking about there is that the first module that will be completed has no less than 25 seperate tables. Whereas the next module has no more than 12 tables. Others will have just 6 or 7 tables, and yet others will have HUNDREDS of tables with ease. It's easier to use a lot of dynamic fields to specify the amount of tables, the format, and the function, than to stick with dynamic. Especially since the format and function of each table is wildly different from module to module. ;(

>Now, using CREATEOBJECT in code to instantiate the module you only have to do an Object.Destroy to wipe it clean. And you only have to do the same to release the middle tier object.

Hrmm, I think it's time I looked up CREATEOBJECT in the documentation.. never noticed it before. Heh. Some programmer I am! ;D

>This sounds like an application that could be the basis of a nice article....please, write it up when you have it working :-)

Heh, that's just the thing; if this were, say, a DB2 forum, I could write it up, share functional examples, even the basic module interpreter! But it isn't, of course. This is for *real* languages. (DB2 is my least favourite migraine-producer.) And otherwise, in the case of FPW2.6. ;) Tell ya what, though, I can do all the basic concepts and outlines and such. It'll take me some time, but I'll be happy to share it with everyone out there using *REAL* programming languages. ;) *cranks up Word, and starts typing like a madman again* At least it's not more technical writing! ;)