iMIS 10.6 and Windows 7

Has anyone had any experience using the 10.6 release client on a Windows 7 OS? We skipped Vista altogether but will likely upgrade to Windows 7 soon and need to know if upgrading to Windows 7 must be preceeded by an upgrade to iMIS 15.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Hi larrman, We have

Hi larrman,

We have experience using iMIS 10.6 with windows 7; both in a 64 bit environment and 32 bit environment. My recommendation for simplicty is that if you do run it on a windows 7 machine, you run it on the 32 bit version of windows 7 and you set the "Disable Visual Themes" under the compability tab. You can set the compatibilty by right clicking on the iMIS icon and clicking properties.

If you install iMIS natively under Windows 7 64 bit, you will run in to a few issues. The first problem is that you have to set the obdc connections under the 32 bit edition of odbc connection adminstrator. You can find that under the C:\Windows\SysWOW64\odbcad32.exe. The one in the control panel is the 64 bit edition. The second problem you will run in to is that the crystal reports wrapper is hard coded to the crystal reports path in the old 32 bit path. Under the 64 bit edition of windows, 32 bit programs are stored under "c:\program files (x86)\". The only way around that is to copy the crystal decisisions folder over to the old 32 bit path to make it work. This is not recommended.

The only other option under windows 7 64 bit is to run iMIS under "XP Mode". XP mode is available for both the Professional and Ultimate editions. You will also need to have a more recent computer processor to run XP mode since Microsoft requires certain vitrual machine extensions to be in place for the "XP Mode" to work. If you use iMIS as a virual application under XP Mode, you will need to tell Omnis7 to open up the imis4.lbr file under the iMIS10 folder.

As far as iMIS 15 goes, I believe you will be in the same boat with the crystal reports. The only difference is that the odbc drivers will not be a problem.

Thanks,

Sean Irish