>>Hi Gary,
>>
>>>What kind of problems or resource issues exist when including and opening multiple vcx's, say 10 or 15. I'm not having any problems now with 8, just wondering what kind of wall, if any, I might hit.
>>
>>I have about 15, and its OK. But the point of my response is: do you know about the NewObject() function and method? In VFP6, you can use this (instead of createobject() and addobject()), and you specify the classlib as a parameter so it doesn't have to be in memory.
>
>Don't know, but I know 8 is nothing... my ap has in excess of 60... of course most of these are for the Visual FoxExpress framework classes.
>
>BOb

Our App exceeds that substantially. Don't think there is a limit (not even an accidental one). The only limitation I can think of is that occasionally you will want to compile everything in a project rather than just do an incremental compile. The more code you have,the longer this takes. But this is more a function of lines of code than of number of VCXs.

There are actually some good reasons for breaking code into a lot of different VCXs. Think about multi-developer environments for example. You want developer A to be able to modify her code without interfering with devloper B.