To clarify.....
Data in RSLogix5000 SINTs, INTs, and DINTs is always stored as pure signed-binary, regardless of which "Style" is chosen for the tags.
These "Style" selections only affect how RSLogix5000 displays the numbers, and has no effect on what bit patterns are stored in the tag database.
The instructions used on the data do not "interrogate" the Style, they merely manipulate the data in the assumption that the programmer is using the appropriate instructions for the data that is stored.
In the tag-database, there are two views, Monitor and Edit. The Style selection in the Edit view is the default style that RSLogix always reverts to when the database is opened. The Style selection in the Monitor view is just a temporary style that is applied until the database is closed and re-opened.
Changing either of these Style selections does not change the data that is stored in the tag in any way.
Now back to BudW's problem.
It all depends on what data is stored, not how it is displayed.
If the data has come from a BCD source, then his 16#1234 will be stored as....
0001_0010_0011_0100
...which is 4660 in decimal.
If you COP this into two SINTs, you will get
0001_0010 in the first, and 0011_0100 in the second.
0001_0010 is 20 decimal, or 12 Hex, and
0011_0100 is 52 decimal, or 34 Hex.
The fact that BudW showed his numbers with 16# prefix infers only that his INT location contains a bit pattern that is a representation of a Hex number, and the use of COP is appropriate in this case.