Thanks for the info! Once the SDEBINARY feature class was in the same geodatabase as the view, using the sdetable -o create view worked and I was able to see the view as a 'feature' in ArcCatalog.
With feature classes that use GEOMETRY (SQL Server) as their shape, can those views span databases and use the sdetable -o register command to store the view within a different geodatabase than the feature class?
Also - what type of geometry is 'better', SDEBINARY or GEOMETRY for SQL Server?
Thanks again for the knowledge, been trying to figure what the issue was all day!