Thanks in advance for help
Vanny
Not enough information. What error code or line that generated the error? I
am not familiar with Foxpro ODBC driver, but if this is happening when you
open the connection, check out the connection string, maybe there is
something in it that is no longer supported.
Also, try searching MSKB for "Foxpro ODBC driver 9.0" and similar words.
http://support.microsoft.com/search/?adv=1
Not much help, but here goes ....
AFAIK MS, in general, pulled-the-plug with older FoxPro file versions,
similar xBase databases, and with ODBC, with its newer Fox Pro Drivers. And
unfortunately the only solution generally offered is to migrate to OLE DB.
However, you mentioned "connect to a .dbf file"? If you are not actually
using FoxPro file versions greater than 6, then there are plenty of
alternative DBF ODBC drivers out there. Some free, some expensive. Or just
continue to use the older driver.
hth
-ralph
Thanks
Vanny
"Ralph" <nt_cons...@yahoo.com> wrote in message
news:uPN37XW...@TK2MSFTNGP04.phx.gbl...
cnnDBF.Open "Driver=Microsoft Visual Foxpro Driver; " & _
"UID=;SourceType=DBF;" & _
"SourceDB=" & pstrFileName
I try to find the info how to change the code to work with VFP version 9
driver or what file should be added along ?
Thanks,
Vanny
"Nobody" <nob...@nobody.com> wrote in message
news:%23jleTIW...@TK2MSFTNGP05.phx.gbl...
See:
OLE DB Provider for Visual FoxPro
http://msdn.microsoft.com/en-us/library/0xzsac67(VS.71).aspx
> ... My question is : could this old driver harms the
> other functions of VPF9??
>
Yes. Assuming "harms" means break the ability to work with version 9 files.
None of the new features would be available, as well as several "older"
features have slightly different behaviors and requirements.
I was not suggesting you *replace* the VFP9 Driver, but supply the VFP6 ODBC
driver as well. You can have both available. I only made that suggestion
when it appeared you were using the driver to access DBF or xBase files and
were dependent on ODBC as the connectivity layer.
You can use the newer driver to connect to older versions of FoxPro, as well
as provide a connectivity layer for most data access libraries. Therefore,
*why* do you want to avoid OLE DB? Or why is it important to use an ODBC
driver?
-ralph
[You might also post to a FoxPro newsgroup. You will find people far more
experienced with VFP than I, plus many have struggled with this switch
already.]
� We have a VB6 application that works fine up to version 6 when using
�
I would highly recommend switching to the Visual FoxPro OLEDB Provider as Nobody suggested. The 6.0
version of the ODBC driver is no longer supported.
You could also try the Visual FoxPro forum but I suspect they will tell you the same thing.
http://social.msdn.microsoft.com/Forums/en-US/visualfoxprogeneral/threads
Paul
~~~~
Microsoft MVP (Visual Basic)
The reason we do not want to change to OLEDB b/c we do not want to release a
new code now but find a quick way to allow customers with VFP9 to also run
the job.
I will look for more info in the Foxpro newsgroup.
Thanks again for suggestion
Vanny
"Ralph" <nt_cons...@yahoo.com> wrote in message
news:%23FyJ2gg...@TK2MSFTNGP05.phx.gbl...
I'm not certain that the VFP9 OLEDB driver would require any radical code
changes to your code - it is "backward compatible" to a large degree. Have
you tried it?
Posting to a newsgroup where FoxPro users hang out is a good idea.
-ralph