>I understand there are potential problems using Identity fields in SQL to generate a PK.
>
>1. Trying to return value with @@identity may give value for insert on another table
>2. Problems with replication
>
>What is the best way to get around these problems? Does SQL 2000 have something to help get around #1? We plan to use replication in the future, should we use GUIDs from the beginning and forget identity fields?

If you are planning on using replication in the future, then definitely go with a GUID now.