See crappy pseudo-code below for the basic idea...
PartitionTable is partitioned on a non-PK column. Yet we need the PK column to be the clustered key. Which means the PK must be part of the partitioning. BUT, we have tables that reference the PK as their FK. That doesn't work with having the partition column as part of the PK. Only options I can see are to drop the FK's (would not be a complete tragedy but not really a good idea) or not cluster on the PK, which would be really, really bad for performance. Partitioning on the PK (col_id) rather than col_status is NOT an option.
Any other ideas anyone?
ALTER TABLE PartitionTable ADD CONSTRAINT
PK_PartitionTable PRIMARY KEY CLUSTERED
) ON PART_SCH_STATUS(Col_STATUS)
ALTER TABLE TableLink WITH CHECK
ADD CONSTRAINT Partition_LINK_FK FOREIGN KEY(Col_ID)
REFERENCES [PartitionTable] (Col_ID)