Up to and including Crystal Reports 2008 v. Though a bit of a review explanation taking us all the way back to CR. SubInACL is a commandline tool that enables administrators to obtain security information about files, registry keys, and services, and transfer this. Windows XP includes ClearType subpixel rendering, which makes onscreen fonts smoother and more readable on liquid crystal display LCD screens. D6GZznACok/TmY-FY_gCiI/AAAAAAAAACE/dwfS79uqGww/s1600/Activex_01.jpg' alt='Uninstall Crystal Reports Activex Viewer Download' title='Uninstall Crystal Reports Activex Viewer Download' />How do you spell confusion CR for VS, Crystal 2. Card Credit Cvv2 Iii Level Software Store. BI 4. x and the. NET SDKs. Up to and including Crystal Reports 2. Though a bit of a review explanation taking us all the way back to CR 1. After Crystal Reports 2. CR 2. 00. 8, things get confusing and in this blog I want to try and remove the confusion and frustrationSo, CR 1. Crystal Reports Basic for Visual Studio 2. Crystal Reports 2. This was a bundled version of CR that was included for free with Visual Studio 2. It had both 3. 2 bit and 6. Now, lets skip to CR 2. CR XI v. 1. 1. x and CR XI R2 v. The install of these versions of CR included the SDK for VS. NET. 3. 2 bit only. However, perhaps to make up for the lack of 6. Crystal Reports SDK for VS, you also got the In. Proc RAS SDK, which is way more functional and includes Report Creation APIs. OK. Were up to CR 2. What should the next version be Well, version 1. And Crystal Reports for Visual Studio 2. CRVS2. 01. 0 is born. Note that this version, follows in the footsteps of CR 1. VS 2. 01. 0 IDE. E. CR XI R2 or CR 2. CRVS 2. 01. 0 has both 3. And it has the Crystal Reports SDK for. NET as well as the In. Proc RAS SDK. And its FREE. All good. What will the next version of CR be How about SAP Crystal Reports 2. What should the file versions be Version 1. One gotcha though NO SDK. None. Not for VS, not for Java. Now, at this point this is not particularly bad as reports created in CR 2. Right. Now lets release BI 4. Business Objects Enterprise 3. File version is 1. And, it has a. NET SDK version 1. All good, except for at least two gotachas BI 4. SDKs cannot be used for unmanaged applications. E. g. reports must be run via managed applications only. You cannot mix version 1. E. g. do not add Crystal. Decision. Crystal. Reports. Engine assembly of version 1. Business. Objects. Enterprise. of version 1. More on point 2 below Mixing versions NO, NO, NO, NO, NO. Now, just to confuse things a bit more, what do we call CR that can work with Visual Studio 2. How about SAP Crystal Reports, developer version for Microsoft Visual Studio. And lets give it version 1. Oh and yes, it does work with VS 2. Wonder about Crystal Reports for VS 2. Me too. Mixing versions NO, NO, NO, NO, NOIn the days of CR 2. BO 3. x, all files were versioned as 1. Thus you could do something like the following Report. Document. Loadmy. Info. Object, my. Enterprise. SessionThe above is an overload that uses RAS to bridge to BOE. It will  use the RAS server in the back end. However, since Report. Document is defined in the CR SDK and Info. Object Enterprisesession is defined in the BO BI SDK, when you move to BI 4. E. g. when migrating from BO 3. BI 4. x it is imperative to avoid this type of code. Remember, the 4. x runtime is only supported for fully managed scenarios and the reportdocument SDK is only supported in the 1. Therefore, the. Load overload and any BOE dependencies were removed from the 1. Just as word to a simple solution to those running into an app that uses the above The application already has the info. Object, so most of the work is done. To set parameters logons to the reportdocument object, use Crystal. Dessions. Enterprise. Desktop. Report objectcast the Info. Object to a Report object and use PSReport. Factory for the reportsource  or Report. Client. Document  object create Report. App. Factory from enterprisesession and create Report. Client. Document from Report. App. Factory. Opendocument Info. Object. ID. Well, that is it. Still confused Below is a handy dandy matrix that may help. File version is not the same as Assembly version Crystal Reports for Visual Studio 2. Future versions for SAP Crystal Reports, developer version for Microsoft Visual Studio version 1. E. g. 1. 3. 7, 1. Managed only. Still more questions Dont forget to search for answers using the search box at the top right corner of this web page. Or, start a Discussion in this Space.