>>>SET DEVELOPMENT ON < s >
>>
>>:-)
>>
>>>otherwise, beats me. It doesn't seem to be a very sensible topic, the way it's phrased.
>>
>>Someone asked if there were any options during install regarding distributed apps. I couldn't remember any.
>
>That was me Evan :) I had read in a study guide that one of the NT cert exams asks what you get with an NT Minimum install.
>
>You may want to take a look at the VFP help on installing VFP. In particular it mentions:
>
>Minimum installation - What are the minimum files need to run VFP?
>
>Complete - What files do you get with this? Are all the things you need for Distributed apps included?
>
>All - The whole enchilada. Is neccesary?

Just about. I think that a number of issues will exist, including source file control, common shared configurations using CONFIG.FPW or the equivalent, clock synchrnization for coordinating developers, class library maintenance. There's a ton to this topic from the standpoint of VFP Development configuration, especailly when the common development environment issues arise - for example, what happens if you try to compile a module that someone else is testing. Without some sort of version control, how do you avoid one developer's changing a source module starting with an old version of the file, losing someone else's changes in the process.

>
>Also look at configuring VFP, ie. what are all those options under the Remote data tab in the options dialog for?
>

Another ball of grunge - network database administration. Just how badly can someone break something in a VFP app when making a change to the back end?

>What about ODBC? What drivers come with VFP? Should they all be installed? Are there others drivers that should take precedence?
>

Probably addressed above, but worth considering, especially with SPT. Remote views are somewhat more immune to ODBC driver variants, since VFP will use the ODBC driver to talk to the back end, but then, a whole new ball of wax when one person gets decent performance with one driver, while some else complains bitterly and vehemently about performance with another, older driver. And then we get into what do we send out with the app?!?!?

And a whole area left unaddressed - how best to construct an install using Setup Wizard for distributed apps...

Just when you thought it was safe to go back in the water!