C1 Community

Is there any way that I can get a version of the Report Designer for .NET 2.0 compiled to run in x86 mode only?  It would be ideal if you could provide 2 versions of the Report Designer for .NET 2.0.  One that you compile with x86 only specified and then one that does not restrict the CPU choice.  The OLEDB provider for Access will only work in x86 mode.  I can compile my programs that use the Reports Components to use x86., but I cannot change the Reports Designer.

I tried using the Reports Designer for .Net 1.X but it can't preview the reports built in the 2.0 version of .NET unless I remove the following from the Connection string in the XML file for the report. "Jet OLEDB:System database=C:\Documents and Settings\DonB\Application Data\Microsoft\Access\System.mdw"   Can I remove the additional specification and then build the XML file in the .NET 1.X and use the XML file with the Report component for .NET 2.0 and the WebReport for ASP.NET 2.0?

I am running on Vista x64 and a little frustrated that I can not use the Reports Designer to finish my applications that were started on a Windows XP x86.  I understand that this is a problem caused by Microsoft not supplying the x64 OLEDB provider for Jet (access) 4.0.

Having an additional version of the Report Designer for .NET 2.0 compiled for x86 only would be the ideal  for me.  But if I can use the Report Designer for .NET 1.X, then I can get by.

Thanks for your input and help. 

DonB

<DonB> wrote in message news:203262@10.0.1.98...

Is there any way that I can get a version of the Report Designer for .NET 2.0 compiled to run in x86 mode only?  It would be ideal if you could provide 2 versions of the Report Designer for .NET 2.0.  One that you compile with x86 only specified and then one that does not restrict the CPU choice.  The OLEDB provider for Access will only work in x86 mode.  I can compile my programs that use the Reports Components to use x86., but I cannot change the Reports Designer.

I tried using the Reports Designer for .Net 1.X but it can't preview the reports built in the 2.0 version of .NET unless I remove the following from the Connection string in the XML file for the report. "Jet OLEDB:System database=C:\Documents and Settings\DonB\Application Data\Microsoft\Access\System.mdw"   Can I remove the additional specification and then build the XML file in the .NET 1.X and use the XML file with the Report component for .NET 2.0 and the WebReport for ASP.NET 2.0?

I am running on Vista x64 and a little frustrated that I can not use the Reports Designer to finish my applications that were started on a Windows XP x86.  I understand that this is a problem caused by Microsoft not supplying the x64 OLEDB provider for Jet (access) 4.0.

Having an additional version of the Report Designer for ..NET 2.0 compiled for x86 only would be the ideal  for me.  But if I can use the Report Designer for .NET 1.X, then I can get by.

Thanks for your input and help. 

DonB

---

http://helpcentral.componentone.com/cs/forums/p/74759/203262.aspx#203262

The report designer in the new v2 drop: 

http://prerelease.componentone.com/dotnet20/c1report/2008-t2/C1Report.2_2.0.20082.50031.zip

is compiled to run in x86 mode, and works fine on Vista 64.

But please note that if you switch to using the new build in your projects (you do not have to do that right away in order to start using the designer app, BTW), you will have to make some (trivial) changes to your code. Specifically:

• The namespace of the C1Report and related classes has changed from C1.Win.C1Report to C1.C1Report.
• The C1Report component is now shipped in C1.C1Report.2.dll, while the C1.Win.C1Report.2.dll now contains the WinForms preview controls. 

In 2008 v2 release, we made significant internal changes to the report. It now shares a lot of code with preview, and shipped as two dlls: C1.C1Report.2.dll contains C1Report and C1PrintDocument components, while C1.Win.C1Report.2.dll contains the preview WInForms controls, which now can preview a C1Report "directly" (i.e. you can assign a C1Report object directly to the Document property of the preview). Hence the above changes. Hope this makes sense/helps.