Handling Crystal Reports in Dynamics SL

SL User is moving to Dynamics SL 2011 upgrading. Migrating customizations from SL 6.5 or SL 7.0 to SL 2011 has gone fine, on the other hand custom reports need an exact manner to ensure a smooth alteration. They can differ, but usually issues have to do “Report Execution” error messages when previewing a Report.

This concern is easily resolute by succeeding these steps:

1. Open the problematic report in Crystal Reports
2.  Go to the Database menu and select “Set Data source Location”

   3.  The “Set Data source Location” dialog opens. The top half is the current data source; the second is the  

    replacement data source. Each table and/or view involved in the report is listed at the top. If there are

 multiple instances of the same table, the Alias will appear before the table name in parenthesis. For

example, Ship Country (Country) – Country is the table name, Ship Country is the alias.   

 

4.  In the Replace with section, expand Create New Connection > ODBC

5.  When you expand ODBC, a list of data source names will appear, select the appropriate database, then press Next

6.  Enter the SQL Credentials press Finish.

7.  Select the first table/view on the Current Data Source and locate the matching table/view in the Replace With. Press Update.

8.  Repeat step 7 for ALL tables and views, including sub reports. Save the report and you will no longer see the error message! Before login Dynamics SL.

Customizations fail on 64-bit server

Issue:

Export the customization's on my development machine (32 bit). After import that customization's in  server (64bit). The customization's are in place and work as expected.

When the user closes the screen, then later opens the same screen errors begin to occur:

When this screen is closed "normal", non-customized version of the screen is loaded.

When the users closes Dynamics SL completely, then reopens SL, a different error is displayed when they try to open the same screen as before:

After clicks OK the screen will invoked and also working fine.

That problem does not occur on my development machine that is running windows 7 32 bit. It only appears to occur on the 64bit platform.

Solution:

• Log off from Microsoft Dynamics SL.

• Browse to the Microsoft Dynamics SL program files directory.                                                                               Path   C:\Program Files\Microsoft Dynamics\SL\Applications\

• Locate the Solomon.ini file, and then open the file by using Notepad.

•      In the Customization section of the Solomon.ini file, make the following change:

                     1.  There was not a [Customization] section in solomon.ini file, so added the following lines:
                                    [Customization]                                
                                          VBASourceCompile = Yes

• Click Save, and then close Notepad.

After this change was made I restarted Dynamics SL on my 64-bit server system and all customization's appear to be working normally.