Re: VFPOLEDB documented bug #607106??
- From: "Craig Berntson" <iamcraig@xxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 24 Oct 2006 08:39:21 -0600
There are some known issues with the VFPOLE DB provider and VS. You could
post the bug at connect.microsoft.com. Drill down into Visual Studio and
you'll find VFP listed there. You should also make sure you're using the
latest VFP OLE DB Provider from
http://www.microsoft.com/downloads/details.aspx?FamilyId=E1A87D8F-2D58-491F-A0FA-95A3289C5FD4&displaylang=en
--
Craig Berntson
MCSD, Visual FoxPro MVP
www.craigberntson.com
Salt Lake City Fox User Group
www.slcfox.org
www.foxcentral.net
"Jim Walsh" <JnospamWALSH@xxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:%23e9VB0t9GHA.1492@xxxxxxxxxxxxxxxxxxxxxxx
I have been having a problem that seems to be falling through the cracks.
Is it a VFP problem? or a VS2005 problem? or an OLE DB provider for Visual
FoxPro problem? Maybe someone here can help clarify this and point me in
the right direction.
I posted a bug report to the Visual Studio 2005 C++ team. The problem that
I am having is that an attempt by me to use the VS 2005 ATL OLE DB
Consumer Wizard to generate a class to connect to my VFP database via the
OLE DB provider for Visual FoxPro crashes the wizard and VS 2005 IDE along
with it.
They responded to my bug report with the following:
"We have investigated issue and it seems that problem code lies within
vfpoledb.dll, which is MS OLEDB Visual FoxPro provider. We will followup
with Visual FoxPro team for further investigation."
When I asked about how I could check on the status of this, they said:
"Unfortunately, MSDN feedback forum cannot be used to track this issue
further. Please contact PSS regarding VSWhidbey bug# 607106 which is used
to track issue in Visual FoxPro OLEDB provider."
At that point, the closed my incident.
I'm in limbo, and don't know where to turn.
Thanks for your help.
Jim
.
- References:
- VFPOLEDB documented bug #607106??
- From: Jim Walsh
- VFPOLEDB documented bug #607106??
- Prev by Date: VFPOLEDB documented bug #607106??
- Previous by thread: VFPOLEDB documented bug #607106??
- Index(es):
Relevant Pages
|