Because I am testing Microsoft Vista™ RC1 and I was curious to see Navision on Vista™, I tried to install it. Installation is not a problem. Native client is working without problems too. But biggest problem is a so small part of Navision as MDAC version detection is. This is biggest problem when you want connect Navision to some MS SQL server. You will got error about wrong MDAC version. Source of problem is the unified versioning of all DLL which are part of the 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 under Vista™, the file has version 6.0.5600.16384 and this is “less" than requested version. Changing MDAC detection in Navision is no way.
But after some “hacking” you can succeed. There is the workaround:
Prepare the modified DLL:
- You need some resource editor tool, for example the Resource Hacker application
- Copy the file sqlsrv32.dll from your Vista system32 folder to another place.
- Open this copy in the resource editor
- Change FILEVERSION value to new value e.g. 2000.85.1117.0 (in the header of Version info ressource)
- Compile the resource
- 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:
- Open properties of the original file
- On the Security tab click Advanced
- On the Owner tab click Edit
- Select new owner of the file, for example your account
- Commit all changes
- Change permissions for your account to have all rights
- Commit all changes
- Now you are able to delete the file – delete it
- Copy the modified file into system32 folder
Now, you are ready to use Navision with SQL Option under Vista™!
I hope, that this will help you to be able to test Vista™ when you are working with Navision.
I tested it on Vista™ RC1 and Navision 4.00SP2+rollup update.
Of course, all this you are doing on your own risk. This is not official workaround and is not supported in any way. Changing original files in any way can be prohibited with local law or license policy.