Local database functionality that is....

>Quite frankly, people outside of the VFP Community don't care that Visual Foxpro can do components or that it integrates with MTS. VFP's biggest strength is its built in database functionality. This should be demonstrated.
>
>>Quite frankly, Craig would be better off showing VFP in a positive light. The worst thing that he could do is go in with the mindset of "showing up" VB or any other too. With 15 minutes, the best course of action is to show how easy it is to build a VFP component, show how easy it is to be hosted in MTS, and then to show how it can be called from an ASP page. And, as a bonus, sneak in something on Macro Expansion...
>>
>>What does this do?
>>
>>1. It shows that VFP can play in the COM space.
>>2. It shows how easy it is to build COM Components in VFP.
>>3. It shows that VFP Components can be called from ASP, like any other COM Component.
>>4. It shows a capability of VFP, Macro Expansion, and at the same time, without "showing up" VB.
>>
>>That in a nutshell, is the formula for success....
>>
>>
>>
>>>>>I was thinking of showing (those VB type people) that VFP works great in data sources other than its own and taking advantage of Windows API feactures.
>>>>
>>>>Windows API isn't going to impress them. They can do API in VB, and probably better. Accessing SQL, using XML, web stuff...that's where it's at.
>>>
>>>I think you would be better off trying to show VB programmers that Foxpro is a better alternative than Access. You are not going to convince any VB programmer to switch to Foxpro to do Components. It's just not going to happen.