Are you volunteering? ;-)

>Might - Or maybe just a white paper to put in the library here.
>
>
>>Absolutely. Again, it'd make a fine article, eh?
>>
>>>And it makes a difference whether programmers are working in adjacent cubicles on the same network or are communicating via email, ICQ and PCAnywhere from around the world. It just isn't feasible to log into a PCAnywhere site 3000 miles away to check out a library - and then find it's checked out to someone 1000 miles the other way, and he isn't on line to discuss it.
>>>
>>>>Interesting. You know, I'd really like to see someone publishing articles with real-world solutions and answers to multiple programmer environments in VFP and how it affects design and architecture. Getting tired of "all theory, no real-world" stuff.
>>>>
>>>>>Even with version control this can be a problem with multiple programmers. We've found it better to break things up into smaller less-composite units so one unit can be upgraded without affecting multiple people's work for a day or two.
>>>>>
>>>>>>Frankly, I usually have one big composite Form-based class with buttons for everything and use this for data entry. If I have any special processes that are repeated within the app, I'll have a composite for those, too.