Where do I get Crystal_regwiz merge modules?

[Tom Jones]

I have an application that was originally built using Visual Studio 2003
that I upgraded to Visual Studio 2005. When I attempt to build the *.msi
file in the deployment project, I am getting a compile error stating that it
cannot find: "C:\Program Files\Common Files\Merge
Modules\Crystal_regwiz2003.msm"

I am not sure where to get this file or even if it is appropriate (i.e.,
should there be a newer version for Visual Studio 2005).

[=?Utf-8?B?SHVzYW0gQWwtQScnYXJhag==?=]

Hi,
Make sure that you have the following merge modules in your setup project :

1)Crystal_Managed2003.msm
2)Crystal_Database_Access2003.msm
3)Crystal_Database_Access2003_enu.msm
4)Crystal_regwiz2003.msm

Hope it will work

Husam Al-A'araj

"Tom Jones" wrote:

I have an application that was originally built using Visual Studio 2003
that I upgraded to Visual Studio 2005. When I attempt to build the *.msi
file in the deployment project, I am getting a compile error stating that it
cannot find: "C:\Program Files\Common Files\Merge
Modules\Crystal_regwiz2003.msm"

I am not sure where to get this file or even if it is appropriate (i.e.,
should there be a newer version for Visual Studio 2005).

[andy]

On 11 Apr, 23:36, "Tom Jones" <[e-mail]:

I have an application that was originally built using Visual Studio 2003
that I upgraded to Visual Studio 2005. When I attempt to build the *.msi
file in the deployment project, I am getting a compile error stating that it
cannot find: "C:\Program Files\Common Files\Merge
Modules\Crystal_regwiz2003.msm"

I am not sure where to get this file or even if it is appropriate (i.e.,
should there be a newer version for Visual Studio 2005).

Those are the 2003 merge modules rather than 2005.
Did you really upgrade both the reports and viewers?
Check your references?
Something still thinks it hasn't been upgraded.

I also don't see why it would be looking for the merge modules unless
your install tells it to.
You can build an install without the crystal stuff.
There again I don't usually go for msi.

Anyhow.
All the merge modules and instructions ( which you should read) are
available for download off the crystal site.
Merge modules:
http://support.businessobjects.com/d...modules.asp#07

You will note that they're not whatever_2003... for crystal in net
2005.

[Tom Jones]

I did the automatic upgrade to 2005 when I opened the 2003 solution... I
gather this does not upgrade the Crystal components.

I am not sure why it is looking for merge modules in the deployment project.
I am not that familier with this and the gentleman who created the
application left the company and there is little documentation or internal
knowledge. I am not that familier with how the deployment project is
configured, but was thinking the merge modules might have been explicity
referenced... but I am just guessing.

Regardless, I would like to use more current versions of Crystal if that is
available and appropriate... just need to figure out what and how to do it.

"andy" <ao***@lycos.co.ukwrote in message
news:11*********************@q75g2000hsh.googlegro ups.com...

On 11 Apr, 23:36, "Tom Jones" <[e-mail]:

>I have an application that was originally built using Visual Studio 2003
that I upgraded to Visual Studio 2005. When I attempt to build the *.msi
file in the deployment project, I am getting a compile error stating that
it
cannot find: "C:\Program Files\Common Files\Merge
Modules\Crystal_regwiz2003.msm"

I am not sure where to get this file or even if it is appropriate (i.e.,
should there be a newer version for Visual Studio 2005).

Those are the 2003 merge modules rather than 2005.
Did you really upgrade both the reports and viewers?
Check your references?
Something still thinks it hasn't been upgraded.

I also don't see why it would be looking for the merge modules unless
your install tells it to.
You can build an install without the crystal stuff.
There again I don't usually go for msi.

Anyhow.
All the merge modules and instructions ( which you should read) are
available for download off the crystal site.
Merge modules:
http://support.businessobjects.com/d...modules.asp#07

You will note that they're not whatever_2003... for crystal in net
2005.

[Carlos Camargo]

Tom,

download the merge modules from the site that Andy told you.

One the cr_net_2005_mergemodules_mlb_x86.zip.ZIP file you download is the
merge module file and a very detailed, step by step, document on deploying
an application that uses Crystal reports.

best regards
"Tom Jones" <nf*@nospam.comescribió en el mensaje
news:e9**************@TK2MSFTNGP05.phx.gbl...

>I did the automatic upgrade to 2005 when I opened the 2003 solution... I
gather this does not upgrade the Crystal components.

I am not sure why it is looking for merge modules in the deployment
project. I am not that familier with this and the gentleman who created
the application left the company and there is little documentation or
internal knowledge. I am not that familier with how the deployment project
is configured, but was thinking the merge modules might have been
explicity referenced... but I am just guessing.

Regardless, I would like to use more current versions of Crystal if that
is available and appropriate... just need to figure out what and how to do
it.

"andy" <ao***@lycos.co.ukwrote in message
news:11*********************@q75g2000hsh.googlegro ups.com...

>On 11 Apr, 23:36, "Tom Jones" <[e-mail]:

>>I have an application that was originally built using Visual Studio 2003
that I upgraded to Visual Studio 2005. When I attempt to build the *.msi
file in the deployment project, I am getting a compile error stating
that it
cannot find: "C:\Program Files\Common Files\Merge
Modules\Crystal_regwiz2003.msm"

I am not sure where to get this file or even if it is appropriate (i.e.,
should there be a newer version for Visual Studio 2005).

Those are the 2003 merge modules rather than 2005.
Did you really upgrade both the reports and viewers?
Check your references?
Something still thinks it hasn't been upgraded.

I also don't see why it would be looking for the merge modules unless
your install tells it to.
You can build an install without the crystal stuff.
There again I don't usually go for msi.

Anyhow.
All the merge modules and instructions ( which you should read) are
available for download off the crystal site.
Merge modules:
http://support.businessobjects.com/d...modules.asp#07

You will note that they're not whatever_2003... for crystal in net
2005.