Re: How to point Crystal Report to the DLL as a datasource?

Hello,

Thanks for the reply.

I am still wondering isn't there a universal - vendor independent - way of pointing Crystal Report to a DLL it is trying to find? 

I googled that but to my surprise did not find anything substantial.

The report I am dealing with was heavily customized, and Sage people usually respond with "Please use a generic report" - which runs ok in a new version.

So I have a choice here:

1) To take a generic report that works in a new version as a basis, and redo all customizations. What makes it worse people that started these customizations are no longer available so I need to go a path "Find all differences in these pictures"

2) To take customized report that works fine in old version, and point it to a new DLL.

Besides saving a lot of time, Option 2 may let me learn how to deal with similar situations.

Here is what I see in report that works:

What is interesting, there is not even a folder with such path on that computer – and the report runs!

And here is what I see in the report that does NOT work:

And although I created a folder with such a path and copied a DLL there, the report still cannot find it ;(

Big confusion. Any insights appreciated.