Imagine this ---

You’re walking into a prospect or customer who wants a demo. You pull out your laptop,
start it up, access the VPC image (and now wait for 15 minutes for things to cache and begin
running). Or better yet, are you always apologizing for the screens to load during your presentation?

Sound familiar? Well, we know of a few things that will make this experience not so dreadful and improve the overall perception of the system performance.

Try these things for a better overall performance with the VPC image:

1. Use an eSata (external SATA) drive to store and access your image. (For additional information on benefits of eSata drives visit http://www.serialata.org/esata.asp.)

2. Allocate 3 gigs of memory to the image

3. Undo Disks – turn this setting on. With Undo Disks turned on, upon completing a presentation you can delete the changes and the next time you start the image it will be as though the other demo never occurred. With this option not selected, any changes done in the image will be saved. Having Undo Disks turned on helps when using the Microsoft Dynamics SL 7.0 Sales Demo VPC image by allowing you to start an image prior to the demo, doing a Save State, and then when you are ready to use the image all of the services would be started already. There wouldn’t need to be the 10-15minutes of prep for the image’s services to load. If you are using an eSata drive you can have everything up and running within 2-3 minutes.

To correct the error "System Message 10202" that occurs when changing the currency ID in the Landed Cost Receipt Entry (61.010.00) sub screen of the Receipt/Invoice Entry (04.010.00) screen in Microsoft Dynamics SL 7.0 SP1, download Hot Fix 16591 LC.

You may notice performance issues when saving, releasing, or posting various batches in Dynamics SL.  This can happen when:

- You are using SL 7.0 or higher
- You are using Windows Authentication
- You have FRx 6.7 Service Pack 10 installed

Because of a bug in the FRx triggers, when all of the above are true a time consuming statement is run each time a record is inserted into the GLTRAN table. Go here for more information and a corrected script.