Problem with BDE apparently caused by Fast Reports
I am a new user to Fast Reports, and created a report running under C++ Builder 6 that accesses a BDE table. The report works fine, however other BDE applications on this machine no longer work - I get the message "Unable to Load Driver" when I run anything else that uses the BDE, even Borland's BDE-based database desktop. The Fast Report itself continues to work. This error only happened when I connected the report to a BDE table. When I first installed the software, and was trying to familiarize myself with it by connecting using ADO there was no problem, so whatever happened only happened when I used it with the BDE.
If I remove the form containing the report from my application and run it on a different machine the application runs without any problem. I checked the folder \Program Files\Common Files\Borland Shared\BDE and nothing has a new time stamp, so I suspect that whatever happened was in the registry.
It is urgent I get a fix for this, any suggestions would be appreciated.
Thank you,
Dave K.
If I remove the form containing the report from my application and run it on a different machine the application runs without any problem. I checked the folder \Program Files\Common Files\Borland Shared\BDE and nothing has a new time stamp, so I suspect that whatever happened was in the registry.
It is urgent I get a fix for this, any suggestions would be appreciated.
Thank you,
Dave K.
Comments
what level and build no of fr
are you using internal datasets or external(frxdbdataset) to connect to data?
i am not a c programmer, but have never had that kind of problem with the Bde in delphi.
We're using the most recent release, I only downloaded it a couple of weeks ago.
The problem happens with both internal and external datasets, as soon as you link the report to a dbf file the BDE breaks. On further testing it even happens using ADO with a DSN pointing to the dbf file - again as soon as you link the report to the dbf file the BDE breaks with the message "cannot load driver". And it's not something in the report itself, testing with an empty report causes the same problem.