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 Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

ODBC for FoxPro Driver from 8.5

Status
Not open for further replies.

modglin

Programmer
Apr 10, 2001
105
I have been creating reports in Crystal 8.5 using my ODBC driver FoxProFile-Word for quite some time. Not sure what has changed, but when I try to refresh one of these reports or try to create a new report I do not get the some options that I used to get.
Previously, when creating a new report I would click on the ODBC driver mentioned above and it would then go to a Configure Connection where I would click ?Free Table directory and indicate O Drive and click OK. It would then listallof the .dbf files and if I clicked OK aain it would then go to Data Explorer and I could add the tables that I needed for the report.
For some reason when I click on the driver now it goes to a Select Data Source screen where it is asking for a DSN name. I am not able to get any further than that to connect to the tables (not really sure what it is looking for). I get this same screen if I click refresh on a report previously created - where in the past it would just refresh.
I went to a computer that has the actual program that these tables are created in and Crystal and she still gets the options that I previously had and it also refreshes any reports that are currently there. I then went to another computer and installed crystal to see if I would be able to create the report. Had to download an ODBC driver for Foxpro, once I did that and tried to create the report, I received the Select Data Source rather than teh Configure connection.
Any ideas as to what could have changed or caused this. Would a change in security for the database (payroll files) have caused the inability to connect even though it does not give that sort of error?
 
If the driver looks different, it's probably the driver.

Check the version.

You probably updated the driver when doing a VFP patch or some such, supported by when you install the new driver it does the same thing.

-k
 
We both have the VFPODBC.DLL 6.01.8629.01. Her's is dated 2000 mine dated 1999 but same version number. She does not have anything listed under the DSN name and neither do I. If I create one, I am able to get to the tables, but since the original connections were through the blank DSN if I try to add a table, it indicates that it is coming from two different data sources.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top