>>>>Thanks, Victor and Naomi. I will give it a whirl in the morning.
>>>>
>>>>And possibly the afternoon as well. In the interests of keeping it simple, one thing I didn't mention is there are 66 sub-apps. I wish I were joking.
>>>
>>>I worked on something like that once - the guy had made a bunch of VFP .app files that were called from the main one....I didn't really care for that design too much.
>>>
>>
>>It is taking some time just figuring out what all the pieces are and how they fit together. Once I have that it will probably be nice to release updates as just relatively small APPs, not the whole shooting match.
>
>Did they have multiple developers working on separate modules at one time without source control? I've seen that multiple-app approach when some pieces were done by different developers or it was contracted out. Hate it! (I've also heard one long-term developer actually recommend it in order to allow for updates to just each separate app when required)
>
>I don't mind it when separation makes sense: maybe a separate reporting app or something, but I've seen extremes too (every module in a separate .app) and that drives me nuts to work on it.

That was exactly the case. I have already gotten approval for version control to be implemented. I would not call the coding incompetent but there were some serious flaws in the overall development methodology. Actually you wouldn't even call it a methodology, more like slinging code at the immediate problem in a vacuum.