Good Morning Kevin,

>>Unfortunately, it looks like you're running into issues with the VFP OLE DB Provider. I've run into >>this on the OrderDetails table but haven't had the time to figure out what's up.

Is there any chance that someone at Microsoft is aware of this aberrant behavior? This is of great concern to me. I bought into the .net framework because I thought I could continue to leverage my previous investment in VFP and use a common language (C#) to write all of my future applications for multiple platforms and devices. I was hoping to write new applications for my clients and take their existing vfp databases to new and exciting places.

If there is a problem with the VFP OLE Db provider at this level, does that imply there are other problems that are going to crop up at different levels? Levels that none of my fellow Mortals have experienced yet? I have purposely kept my Jump Start applications connected to SQL data to limit the variables as I climb the learning curve. However, it is time for me to start rolling up my sleeves and begin working in the real world.

You and I have had a common basis for discussions up to this point, in that we are working with the same documents, code and database. How can I now venture off into my own little development world, utilizing a data provider, which is not ready for prime time?

Perhaps we can share this thread with the folks that support the VFP Data provider?
Your thoughts are greatly appreciated.

Neil