"thejamie" <thejamie@discussions.microsoft.com> wrote in message
news:1DEFED9C-70B1-4753-8F32-01E462D3E774@microsoft.com...
> Hi,
>
> I'm getting the error above on a client machine with the deployment. The
> simple part of this is that I don't create a setup for this (which may be
> incorrect) because they are in-house machines preloaded with Crystal and
> SQL
> Server tools. I am trying to rule out the possibility of an incorrect
> reference for the Crystal Report which may be the wrong way to solve this,
> but the one which I am focussed on.
>
> Two modules, both deploying an activex crystal viewer (crviewer91).
>
> In both projects, I have references to CrystalDecisions.Windows.Forms,
> ReportEngine, the Shared, and ReportSource references. Additionally I
> have
> the Viewer references. I am not certain that I am using a CRAXDRT.dll
> legacy
> app, (so many version on my machine - it gets really confusing - the 8.5
> for
> Macola, the 9 versions I have, possibly a leftover from ver7? ... but
> viewer91 is definitely the viewer that came with my licensed version of
> Crystal 9. As I understand it from Crystal, the version I have is the one
> I
> should use and not the NET reference to Crystal although they did send me
> a
> license for that as well. So, in deference to the above, I am
> referencing
> what I believe to be the 9 versions of the Craxdrt.dll, the crviewer9lib,
> and
> cselexptlib.dll.
>
> The problem seems to be that there are these strange reference creeping in
> that say AxInterop.Craxdrt and Interop.Craxdrt. I believe my confusion
> may
> be that the Viewer for Crystal 9 looks a lot different from the one that
> comes with NET and since I am familiar with this viewer, it is the one I
> prefer to work with. I suspect I may end up going to Crystal and
> submitting
> a support issue, but it would be nice if I could figure out before hand
> what
> the words AxInterop and Interop actually mean.
>
> What is the meaning behind AxInterop and Interop?
> --
> Regards,
> Jamie