Don't think database. Think other things. Complex web services. Service Oriented Architecture. Workflow. etc.

IMO, one of the problems with VFP is it has gotten thinking database first rather than functionality first.

>Craig,
>
>Thanks for your reply.
>
>Regarding your statement 'if the customer base demands .NET' - just what makes .NET so special? Or what can it do that VFP can't from a database app standpoint? (aside from the fact that VFP's umbilical cord will be severed in the future and that M$ is pushing .NET?)
>
>Dennis
>