>>I very recently talked to someone who did a VFP/InterDev project. There is
>>a reason why Access was used in examples only! (s) From what I hear you
>>may be better of to wait until more is done in this area with VFP.
>>Supposedly the MS Tech support people had to really struggle to give any
>>answers on how to use VFP with InterDev. I hear there very little has been
>>done in this area.
>>
>PMFJI, but we have a gentleman in our user group who actually showed this
>at work at our March meeting *before* DevDays launched it.
>
>The problem with VFP was that the ODBC driver that VID has to use was not
>yet able to work in that new environment. After some pressure of a few
>fanatical Fox users (including me), MS put the new ODBC driver up on their
>web page just days before the March 19th DevDays launch of Visual Studio.
>
>Because this ODBC driver was brand spanking new, there was no substantial
>work done with VFP and VID. Of course, MS Access was in a different position
>and, of course, that product was on the bleeding edge to work with VID at
>that time. But, I would say that VFP5 works fine with it now, but you
>probably need both the VFP5.0a release and the newest ODBC driver to really
>gurantee that it has a chance. Our group member though was able to get it
>to work with VFP5.0.
>
>==Carl

It took a lead InterDev tech support rep a few days working with my buddy to figure out how to use VFP with InterDev. This included phone calls in both directions to get things together. If you guys have it working you may want to show the InterDev support team how you did it.

Thanks
Tom