I agree with all the detailed and excellent information given by dmargineau, but help me assure myself that he didn't blow right past something simpler.
Help me understand this:
A PB32 database was imported into FctMeViewStudio.
The original app was a DF1 terminal, so this should have generated a shortcut matching the node name from the PB32 app.
Last time I used this tool, it used HMI tags for everything, and it is useful to clean up the PB32 tags first (homogenize tag names descriptions, etc.).
When I used this tool, I got four pages of errors due to the heavy use of oddball data types (character arrays of N files) that would not convert, but everything else worked (in test mode) once I "laid hands on" the shortcut in the RSLinx Enterprise browse window. Even if it looks right, click on it again, and say okay if you suddenly start losing communication after messing with a shortcut.
In your case, you need to point the shortcut at the new target on the Ethernet network. If you are not connected live and online, you can right click on the Ethernet area of the Target Tab browse window and find a hidden place where you can manually add a Micrologix and give its IP address.
I use HMI tags exclusively with SLC/Micros, since direct referencing is of zero advantage and too restrictive for any HMI application I have ever created.
When you get it all working, you now need to add more stuff to this HMI to access those other PLCs. Assuming these other Micrologix are copies of the first:
First, add a new shortcut for each of the PLCs and set their IP addresses. They each must have a unique name.
Second, in the HMI tag list, I would recommend that you make a new folder and give it a name similar to the first PLC shortcut name. Next, move all of the tags referencing that controller into your tag folder. Triplicate the folder. Triplicate all your Displays, alarms, navigation facilites, and controls, etc. Find and replace all the tags in the copies to correct the folder portion of the expressions for each of the PLCs.
Piece of cake, right?
I might be mis-remembering about the import process making HMI tags, I may have blunted them in there with my own fat fingers.