Liveware Publishing Support Forum

While my report runs fine in R&R SQL designer, I receive an error when I try to run the report in Visual Basic 6.____The error I receive is:____"DB access[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified"____Any help would be appreciated. We are using R&R SQL Edition v11.

Yes. The report runs fine when I use either rsw.exe or rswrun.exe.____If I use the latter I must manually select the Access Database. If I use rsw.exe then I don^t have to select the Access Database.____Might RSWSQL.ini be the source of the problem?__

If the datasource has been set up to point to the MDB file, you should not need to select it when you run the report using rswrun.exe.____I just tried two test reports using access data sources and as long as the mdb was selected when the data source was configured in the ODBC manager, it works fine for me.____What you can try is adding a section called DATABASE to your c:windows sw.ini file. In that section add the line:__USEQECONNECT=1__and see if that helps.____Are you running the OCX from the same development machine as rsw.exe?____Kathleen__R&R Support

If you double click execute RSW.EXE and select the report does it run without an error?____Kathleen__R&R Support

__>Are you running the OCX from the same development machine as __>rsw.exe? __>__>Kathleen __>R&R Support ____Yes I am. The R&R SQL OCX cannot find the Access driver. My app conntects to the Access database just fine. But the OCX control does not. Dunno why.

I solved the problem. It is not clear from your manuals what the term DataSource means.____I was using the DataSource parameter as the name of the Access database, i.e. Client.mdb. In fact, DataSource means DataSourceType. When I replaced "Client.mdb" with "MS Access Database", the report works fine.____I guess I am just a noob. Sorry to have wasted your time on this.

>If you double click execute RSW.EXE and select the report __>does it run without an error? __>__>Kathleen __>R&R Support ____Yes. This works fine. I receive this error only from inside my application using the OCX control with an Access database.____We have been using VB with foxpro files for years, but are now moving to Access. Unfortunately, the SQL edition does not work for us.