1. Extended Operating System Support
Supported Operating Systems now include:
Windows 7 Professional SP1 (64-bit)
Windows Server 2008 SP2 R2 (64-bit)
Copyright © 2011 Rockwell Automation, Inc. All rights reserved.

2. Copyright © 2011 Rockwell Automation, Inc. All rights reserved.
64-bit OS Compatibility
Customer Needs
Support FactoryTalk View on 64-bit OS, including:
FactoryTalk View Studio
FactoryTalk View SE Server
FactoryTalk View SE Station
FactoryTalk View ME Station
Analysis
Limiting factor determined to be the Watcom database, used for the FactoryTalk View HMI Tag Database.
Delivering 64-bit OS Compatibility
Replace Watcom database with SQL Server 2008 R2 Express in the FactoryTalk View v6.1 release
Copyright © 2011 Rockwell Automation, Inc. All rights reserved.

3. Challenges when migrating from 32-bit to 64-bit Operating System
All FactoryTalk View releases prior to v6.1 have been exclusive to 32-bit OS computers.
Moving systems and applications from a 32-bit OS to a 64-bit OS can create migration challenges
Helping our customers with the migration
Created Compatibility Guidelines to help customers migrate previous versions of FactoryTalk View applications to FactoryTalk View v6.1 on a 64-bit OS
Created Tag Database Conversion Tool to help with the conversion of projects from the previous database technology to SQL Server Express
Copyright © 2011 Rockwell Automation, Inc. All rights reserved.

4. Common Compatibility Guidelines
FactoryTalk View Projects
Use FactoryTalk View Studio v6.1 on a 32-bit OS to open ME and SE Projects created with pre-v6.1 FactoryTalk View Studio. This action updates the project format to v6.1 and migrates the tag database to SQL Server Express. Once opened using FactoryTalk View Studio v6.1 on a 32-bit OS, the ME and SE Projects can be moved to a 64-bit OS.
FactoryTalk View ME and SE Projects that include a Watcom Database must be converted with the Legacy Tag Database Conversion Tool before they can be opened with FactoryTalk View Studio v6.1 on a 64-bit OS
FactoryTalk View .APA Files
A FactoryTalk View ME or SE .APA file needs to be expanded into a project structure using Application Manager hosted on a 32-bit OS before using the Legacy Tag Database Conversion Tool.
Copyright © 2011 Rockwell Automation, Inc. All rights reserved.

5. Common Compatibility Guidelines
FactoryTalk View MER Files on 32-bit OS
When creating 5.0, 5.1, 6.0 FactoryTalk View ME Run-Time Files (MER) using FactoryTalk View Studio v6.1 on a 32-bit OS, the “Convert to Development” option can be set to either “Allow” or “Never Allow”, since the Watcom database can be included in the MER.
FactoryTalk View MER Files on 64-bit OS
When creating 5.0, 5.1, 6.0 FactoryTalk View ME Run-Time Files (MER) using FactoryTalk View Studio v6.1 on a 64-bit OS, the only “Convert to Development” option is “Never Allow”, since the Watcom database cannot be included in the MER.
Copyright © 2011 Rockwell Automation, Inc. All rights reserved.

6. Legacy Tag Database Conversion Tool
Where do I get this tool?
Posted on the RA Knowledgebase - Answer ID
Included with FactoryTalk View v6.1
What versions of FactoryTalk View ME and SE can I use this with?
Legacy Tag Database Conversion Tool can be used with projects as early as version 3.2
What about RSView32 and PanelBuilder 32 Apps?
Legacy Tag Database Conversion Tool also supports converting RSView32 and PanelBuilder 32 projects.
Do I have to convert each project separately?
Legacy Tag Database Conversion Tool can perform single or multiple project conversions
Copyright © 2011 Rockwell Automation, Inc. All rights reserved.

7. Other options to use FactoryTalk View on a 64-bit Computer
Windows XP Mode
Technote Support of Rockwell Automation Software in Windows XP Mode in Windows 7
Use XP MODE on 64-bit Windows 7 Professional PCs
Requires free download from Microsoft
Native 64-bit and 32-bit XP Mode Image can share FT Activation
XP Mode not suitable for runtime applications (i.e. hosting Machine Edition Station)
Virtualization or Separate 32-bit PC
Use Separate PC or Virtual Image running 32-bit Windows OS
Could share FactoryTalk Activation with 64-bit PC over network
Copyright © 2011 Rockwell Automation, Inc. All rights reserved.

8. Detailed 64-bit Compatibility Guidelines
Copyright © 2011 Rockwell Automation, Inc. All rights reserved.

9. FactoryTalk View Project Compatibility Guidelines#
Action
Result 1
I have a pre-v6.1 FactoryTalk View SE or ME project that I want to open using FactoryTalk View Studio v6.1 hosted on a 32-bit OS
I can open a pre-v6.1 FactoryTalk View SE or ME Project in FactoryTalk View Studio v6.1 hosted on a 32-bit OS since the Watcom dB can only run on 32-bit OS. The project will converted to v6.1 application format and use SQL Server Express 2
I have a pre-v6.1 FactoryTalk View SE or ME project that I want to open using FactoryTalk View Studio v6.1 hosted on a 64-bit OS
I cannot open a pre-v6.1 FactoryTalk View SE or ME project using FactoryTalk View Studio v6.1 hosted on a 64-bit OS until I open the project with FactoryTalk View Studio v6.1 hosted on a 32-bit OS, or I use the Legacy Tag Database Conversion Tool hosted on a 32-bit OS.
Once the conversion is done, I can copy the project(s) to a computer running a 64-bit OS and open with FactoryTalk View Studio v6.1
(Confidential – For Internal Use Only) Copyright © 2011 Rockwell Automation, Inc. All rights reserved.

10. MER Creation Guidance # Action Result 1
I want to create a 5.0, 5.1, 6.0, or 6.1 MER File from my open HMI project using FactoryTalk View Studio v6.1 on a 32-bit OS
I can create a MER File for versions 5.0, 5.1, and 6.0 that is set it to either Allow or Disallow “Conversion to Development” 2
I want to create a 5.0, 5.1, or 6.0 MER File from open HMI project set to Allow “Conversion to Development” using FactoryTalk View Studio v6.1 on a 64-bit OS
I can only create an MER File for versions 5.0, 5.1, and 6.0 that is set it to Disallow “Conversion to Development”
I cannot create an MER File for versions 5.0, 5.1, or 6.0 that is set to Allow “Conversion to Development” because Watcom database files cannot be packaged in the MER File from a 64-bit OS 3
I want to create a 6.1 MER File from open HMI project set to Allow “Conversion to Development” using FactoryTalk View Studio v6.1 on a 64-bit OS
I can create a MER File for versions 6.1 that is set it to either Allow or Disallow “Conversion to Development”
(Confidential – For Internal Use Only) Copyright © 2011 Rockwell Automation, Inc. All rights reserved.

11. MER Restore to Development Guidance#
Action
Result 1
I want to “Restore” an MER File created in versions 5.0, 5.1, 6.0, or 6.1 of FactoryTalk View Studio on a 32-bit OS to an MED Project using the corresponding version of Application Manager on a 32-bit OS
I can “Restore” this MER File to an MED Project 2
I want to “Restore” a 5.0, 5.1, or 6.0 MER File created in versions 5.0, 5.1, 6.0, or 6.1 of FactoryTalk View Studio on a 32-bit OS to an MED Project using the v6.1 Application Manager on a 64-bit OS
I cannot “Restore” the MER File to an MED Project because the MER contains Watcom database files and cannot be restored on a 64-bit OS 3
I want to “Restore” a 5.0, 5.1, or 6.0 MER File created in FactoryTalk View Studio v6.1 on a 64-bit OS to an MED Project using any version of Application Manager on any OS
Using FactoryTalk View Studio v6.1 on a 64-bit OS I cannot create a 5.0, 5.1, or 6.0 MER File that allows “Restore” to MED Project because the MER File would need to contain Watcom database files which cannot be created on a 64-bit OS
(Confidential – For Internal Use Only) Copyright © 2011 Rockwell Automation, Inc. All rights reserved.

12. FactoryTalk View ME Station Desktop: MER Compatibility Guidelines (1 of 2)#
Action
Result 1
I want to run a version 3.2 or 4.0 MER File created in FactoryTalk View Studio v6.1 hosted on a 32-bit OS using FactoryTalk View ME Station Desktop running on a 32-bit OS.
I can run this MER File using v6.1 FactoryTalk View ME Station Desktop hosted on a 32 or 64-bit OS, or using pre-v6.1 FactoryTalk View Machine Edition Station Desktop hosted on a 32-bit OS 2
I want to run a version 3.2 or 4.0 MER File created in version 6.1 of FactoryTalk View Studio hosted on a 64-bit OS using FactoryTalk View ME Station Desktop running on a 32- or 64-bit OS.
I can run this MER File using v6.1 FactoryTalk View ME Station Desktop hosted on a 32- or 64-bit OS
I cannot run this MER File using pre-v6.1 FactoryTalk View ME Station Desktop hosted on a 32-bit OS 3
I want to run a version 5.0, 5.1, or 6.0 MER File created in FactoryTalk View Studio v6.1 hosted on a 32-bit OS using FactoryTalk View ME Station Desktop running on a 32- or 64-bit OS.
I can run this MER File using v6.1 FactoryTalk View ME Station Desktop hosted on a 32- or 64-bit OS, or using pre-v6.1 FactoryTalk View ME Station Desktop hosted on a 32-bit OS
(Confidential – For Internal Use Only) Copyright © 2011 Rockwell Automation, Inc. All rights reserved.

13. FactoryTalk View ME Station Desktop: MER Compatibility Guidelines (2 of 2)#
Action
Result 4
I want to run a version 5.0, 5.1, or 6.0 MER File set to Allow “Conversion to Development” created with FactoryTalk View Studio v6.1 hosted on a 64-bit OS using FactoryTalk View ME Station Desktop running on a 32- or 64-bit OS.
Using FactoryTalk View Studio v6.1 on a 64-bit OS I cannot create a 5.0, 5.1, or 6.0 MER File that allows “Restore” to MED Project because the MER File would need to contain Watcom database files which cannot be created on a 64-bit OS 5
I want to run a version 5.0, 5.1, or 6.0 MER File set to Disallow “Conversion to Development” created with FactoryTalk View Studio v6.1 hosted on a 64-bit OS using FactoryTalk View ME Station Desktop running on a 32- or 64-bit OS.
I can run this MER File using v6.1 FactoryTalk View ME Station Desktop hosted on a 32- or 64-bit OS
I cannot run this MER File using pre-v6.1 FactoryTalk View ME Station Desktop hosted on a 32-bit OS because the Watcom database files are not included in the MER since it was built on a 64-bit OS
(Confidential – For Internal Use Only) Copyright © 2011 Rockwell Automation, Inc. All rights reserved.

14. Key Frequently Asked Questions
Copyright © 2011 Rockwell Automation, Inc. All rights reserved.

15. Key FactoryTalk Machine Edition v6.1 FAQs
Now that FactoryTalk View Studio v6.1 with 64-bit operating system support is released, can I simply copy my HMI projects and APA files to my new 64-bit computer and start working?
Unfortunately you cannot simply copy the HMI projects and APA files to a new 64-bit computer running FactoryTalk View Studio v6.1 and begin working immediately. The pre-6.1 HMI projects contain database files for which no 64-bit operating system compatible database engine exists. To provide 64-bit operating system compatibility FactoryTalk View Studio v6.1 replaced an older database engine, called Watcom, with Microsoft SQL Server 2008 R2 Express edition.
Before working with pre-6.1 HMI projects with FactoryTalk View Studio v6.1 hosted on a 64-bit operating system, one must either
Open the HMI Projects with FactoryTalk View Studio v6.1 hosted on a 32-bit operating system, or
Convert the projects using the Legacy Tag Database Conversion tool hosted on a 32-bit operating system
Once the pre-6.1 projects have either been opened with FactoryTalk View Studio v6.1 hosted on a 32-bit operating system or converted with the conversion tool, FactoryTalk View Studio v6.1 hosted on a 64-bit computer can open the HMI projects. Pre-6.1 APA files must be fully expanded (restored) and then converted to v6.1 format using either method described above.
If one intends to open the pre-6.1 projects using FactoryTalk View Studion v6.1 hosted on a 32-bit operating system computer then no special steps are required.
Why is it not possible to open my pre-6.1 HMI projects on my new 64-bit computer using FactoryTalk View Studio v6.1?
The pre-6.1 HMI projects contain database files for which no compatible 64-bit operating system database engine exists. To provide 64-bit operating system compatibility FactoryTalk View Studio v6.1 replaced an older database engine, called Watcom, with Microsoft SQL Server 2008 R2 Express edition.
Copyright © 2011 Rockwell Automation, Inc. All rights reserved.

16. Key FactoryTalk Machine Edition v6.1 FAQs
I plan to use the Legacy Tag Database Conversion tool, can I convert all my pre-6.1 projects in one step, or do I need to convert each HMI project individually?
The Legacy Tag Database Conversion tool support both single and batch operation. So it is possible to convert all your pre-6.1 HMI projects in one operation.
Can I import my PanelBuilder32 applications in to FactoryTalk View Studio 6.1 hosted on a 64-bit operating system?
Yes, you can directly import PanelBuilder32 applications using FactoryTalk View Studio v6.1 hosted on either a 32-bit or 64-bit operating system.
I am using FactoryTalk View Studio v6.1 hosted on a 64-bit operating system and I cannot import my RSView32 projects, why not?
RSView32 uses the Watcom database engine. Since the Watcom database engine cannot execute on a 64-bit operating system it is not possible to import RSView32 projects using FactoryTalk View Studio v6.1 hosted on a 64-bit computer.
To import the RSView32 projects in to FactoryTalk View Studio v6.1 one must either
Import the RSView32 projects with FactoryTalk View Studio v6.1 hosted on a 32-bit operating system, or
Convert the PanelBuilder 1400e projects using the Legacy Tag Database Conversion tool hosted on a 32-bit operating system
Copyright © 2011 Rockwell Automation, Inc. All rights reserved.

17. Key FactoryTalk Machine Edition v6.1 FAQs
I am using FactoryTalk View Studio v6.1 hosted on a 64-bit operating system and I cannot import my PanelBuilder 1400e projects, why not?
PanelBuilder 1400e uses the Watcom database engine. Since the Watcom database engine cannot execute on a 64-bit operating system it is not possible to import PanelBuilder 1400e projects using FactoryTalk View Studio v6.1 hosted on a 64-bit computer.
To import the PanelBuilder 1400e projects in to FactoryTalk View Studio v6.1 one must either
Import the PanelBuilder 1400e projects with FactoryTalk View Studio v6.1 hosted on a 32-bit operating system, or
Convert the PanelBuilder 1400e projects using the Legacy Tag Database Conversion tool hosted on a 32-bit operating system
I do not have access to a 32-bit computer, can I use Microsoft Windows 7 XP Mode to run an earlier version (pre-6.1) of FactoryTalk View Studio or the Legacy Tag Database Conversion tool to prepare my pre-6.1 HMI projects for FactoryTalk View Studio hosted on a 64-bit operating system?
Yes, when a computer running a 32-bit operating system is not available the best means to prepare the pre-6.1 HMI projects for use with FactoryTalk View Studio hosted on a 64-bit computer, is to use Microsoft Windows 7 XP Mode. XP Mode is freely download Windows 7 extension that enables a virtualized 32-bit PC running Windows XP with Service Pack 3. XP Mode is available from Microsoft’s website.
Please remember that XP Mode is not suitable for runtime applications. XP Mode should only be used for design activities.
Copyright © 2011 Rockwell Automation, Inc. All rights reserved.

18. Key FactoryTalk Machine Edition v6.1 FAQs
Can I share FactoryTalk Activations between by 64-bit host computer and the virtualized Microsoft Windows 7 XP Mode computer?
Yes it is possible to share the FactoryTalk Activation between the 64-bit host and 32-bit virtualized (XP mode) computers. Please note the Legacy Tag Database Conversion tool does not require activation.
Can I use Microsoft Windows 7 XP Mode with FactoryTalk View Machine Edition 6.1 release?
Yes, however, XP Mode is not suitable for runtime applications. XP Mode should only be used for design activities.
Copyright © 2011 Rockwell Automation, Inc. All rights reserved.

19. Key FactoryTalk ViewPoint v2.1 FAQs
Can my web-enabled mobile phone or tablet be used as a FactoryTalk ViewPoint client?
When Microsoft created Silverlight they created two instances, one is called “In-browser” and the other “Out-of-browser”. FactoryTalk ViewPoint is built on the “In-browser” Silverlight. Thus, the FactoryTalk ViewPoint client can only be hosted on devices that provide “In-browser” Silverlight support. The web browser available on mobile devices (Apple iPhone or iPad, or Android-based phones or tablets) do not natively support “In-browser” Silverlight. So, it is not possible to use the web browser on these devices to host a FactoryTalk ViewPoint client.
How many client connections does FactoryTalk ViewPoint support?
The total number of connections a FactoryTalk View Site Edition Server can support is 50 client connections. This includes both FactoryTalk View Site Edition Clients (thick client), FactoryTalk ViewPoint Clients (thin-clients).
The FactoryTalk ViewPoint Server hosted on a PanelView Plus terminal provides a single client connection at no additional cost.
Will my customers’ existing FactoryTalk ViewPoint licenses enable tag writes when the customer upgrades to FactoryTalk ViewPoint 2.0?
Yes, after the customer upgrades from a previous FactoryTalk ViewPoint version to v2.0 all existing v1.0, v1.1 and v1.2 FactoryTalk ViewPoint Client licenses will provide tag write capability. Rockwell Automation currently has no plans to introduce a Read-Only FactoryTalk ViewPoint Client license. Customers desiring this functionality can do so via security configuration.
Copyright © 2011 Rockwell Automation, Inc. All rights reserved.

20. Key FactoryTalk ViewPoint v2.1 FAQs
Is a customer required to enable and configure FactoryTalk ViewPoint security to enable tag writes?
FactoryTalk ViewPoint applications operate in read-only mode by default when the security system is disabled. However, an administrator can enable tag writes even though security is disabled. This allows any user that can connect to the FTViewPoint server to perform tag writes.
Where can I learn more about which FTView ME objects and capabilities are supported in FTViewPoint?
Knowledgebase article (AID 57596) contains a detailed listing of FTView ME objects and capabilities that are supported in FTViewPoint. This AID is updated following each FTViewPoint release.
Copyright © 2011 Rockwell Automation, Inc. All rights reserved.