Applies to VISTA.

This should be fixed in office 2007 sp2 but if for some reason it is not fixed after the servicepack installation then you can do the following:

Now, MS puts that file there in the outlook.exe folder and if it’s not their
file but some other one things get broken and Outlook can’t start.

If you have that file in your outlook.exe folder open it in Notepad and make
sure it has an entry in there with this text “Microsoft.VC80.CRT”. If that’s
in there it’s the MS file and should be OK. If something else is there you
need to remove it and replace it with the original MS file.

Applies to NAV 4.0 and microsoft sql server 2005.  SQL server 2008 has not been tested yet

There’s a problem when you try to connect to a SQL Server database due to a wrong MDAC detection.

The cause of this problem is the unified versioning of all DLL in Vista.

 Navision is detecting MDAC version through File version of SQL ODBC driver (sqlsrv32.dll). On Windows XP you can see version like 2000.85.1117.0 etc, but on Vista the file has version 6.0.5600.16384 and this is “less” than the requested version. Changing MDAC detection in Navision is no way.

The trick to run Dynamics NAV 4.x on Vista is this:

1. You need some resource editor tool, for example the Resource Hacker application
2. Copy the file sqlsrv32.dll from your Vista system32 folder to another place.
3. Open this copy in the resource editor
4. Change FILEVERSION value to new value e.g. 2000.85.1117.0 (in the header of Version info ressource)
5. Compile the resource
6. Save the file (backup original file!)

Now you need to copy the file back into system32 folder. But under Vista, this is not easy task. The file cannot be changed because just installer has enough rights.

Replacing original file with modified one:

1. Open properties of the original file
2. On the Security tab click Advanced
3. On the Owner tab click Edit
4. Select new owner of the file, for example your account
5. Commit all changes
6. Change permissions for your account to have all rights
7. Commit all changes
8. Now you are able to delete the file – delete it
9. Copy the modified file into system32 folder