First time on here so hopefully I'm posting to the correct location!!
The reason I am asking this is because we installed SP4 on a development machine and it fixed a bug where margin information set at runtime was being lost. We have since rolled back the SP4 install and downloaded the latest merge modules (labelled SP4) and the fix isnu2019t applied when we once again attempt to build our application.
PC is running VS 2010, Any ideas?
Ideally, the "service pack" version of the merge modules will match the service pack for fixes. Differences normally doesn't happen very often, but it is possible. There may be other issues in play here.
If I read your post correctly you said that when you applied SP 4 to your development machine the "issue" went away, but that you then removed SP4 and applied just the merge modules to your development machine and the "issue" returned. This is not a valid test. Merge modules should never be used on a development machine as a path for applying patches, fixes, or updating the Visual Studio IDE. It is expected that you would install the full service pack onto your development machine.
You've also indicated that you're using VS2010. Crystal Reports 2008 isn't supported for application development with VS2010. The supported version of Crystal Reports is CR for VS2010. CR2008 isn't expected to integrate into your VS2010 environment. This means that there's no channel for trying to find out why the SP4 merge modules are "different" from SP4 itself. The environment itself may be contributing to the issue, but there's really no way to know. This would have to be duplicated in a supported environment (e.g. VS2008 with CR2008) before any issues could be addressed.
For reference you can visit the "[Which Crystal Reports assembly versions are supported in which versions of Visual Studio .NET|http://wiki.sdn.sap.com/wiki/display/BOBJ/WhichCrystalReportsassemblyversionsaresupportedinwhichversionsofVisualStudio+.NET]" wiki to see which versions of Crystal Reports are supported in the various versions of Visual Studio.
We have been using VS2010 for development but our .Net platform is framework 3.5. Since you only support VS2008 we have now tested compiling with VS2008 and we have still the same issue
There is also a slight misunderstanding that we don't develop using the merge modules. We develop using Crystal 2008 SP4 and when we build our application for deployment we use the merge modules, and it's when we do a build with this that we have the problems - there is no problem using Crystal Reports SP4 on the development environment
If it helps, the issue we have is when setting margins on reports dynamically at runtime - our margins are all over the place when we have a proper application build and because we have a large number of reports with all margin-related information in the database, changing all reports would require a significant amount of time so if there's a fix we can apply we will choose that