Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

VFP OLEDB Driver

Status
Not open for further replies.

fluteplr

Programmer
Oct 23, 2000
1,599
US
OK I'm confused.

I thought the VFP OLEDB driver was included in the MDAC versions 2.6 and 2.7, but when I installed these on a client machine the OLE VFP driver did not show as an available option when I created a .udl file.

I also thought at one time it was available as a download on the MSDN sight but I just spent an hour looking for it, no luck.

Any one have a clue?
 
A "clue" yes, a solution maybe. The VFP OLEDB is currently only available with VFP 7.0 - if you bought VFP 7.0 you can distribute the VFP OLEDB.

Some have speculated that it hasn't yet been made available in any MDAC package because part of it was dependent on / created with .NET. Since .NET was in beta until a couple weeks ago, MS may not have wanted to release it (VFP OLEDB) until all the .NET components were "officially" finallized. You may see it in MDAC 2.8 now that .NET is "real".

Rick
 
Ah, that would explain it, I have 7 installed on my machine. I can verify that the VFP OLE driver is not dependant on .net though.
 
Actually on my system, it shows that it's using version 7.0.2600.0 of MSVCRT.DLL, which is the .NET (VC++ 7.0) runtime. I don't know if it actually uses any "new" features, but ...

Rick
 
Im trying to use the foxpro 7 oledb provider in vb6 and I have some very sickening results. It took me 6 minutes on my pent iii 650 to load a recordset with 100,000 and filla list box with one field. I was able to fill an entire datatable in 15 seconds with 100,000 records in .NET.. Does this mean that fox7 oledb is unusable with vb6.. please can someone help show me what im doing wrong?? i hope im doing something wrong..
 
First, I believe most developers VFP or VB would question loading a listbox with 100,000 records - normally less than 1,000 (or some would suggest 500) is more realistic. Users can't really need to look at that many records at once.
Also, I'm curious why you compare two different functions - loading a listbox certainly has more overhead than simply loading a "table".

Like most client-server approaches, you should only request part of the data at any given time. I've heard of people successfully using the VFP OLEDB provider in VB 6 just as you would using the one for SQL Server.

Rick
 
For those requirements I would suggest using a 3rd party tool. For example, I use Crystal Reports. It has a subreport capability that makes that feature quite easy. [pc] Oh Tartar Sauce.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top