I'm going to tell you how to cheat. 🙂
Mind you, you'll need to buy the tool I'm recommending but for a newbie (assuming you have MS Access experience at least) this will let you not only solve your issue but two or three others you don't know you're about to run into.
The tool is called ModelRight and while it's not cheap ($595 for the SQL Server only version) it will let you AUTOMATICALLY suck up your MS Access schema into a "database CAD" (actually called an ERD tool), preserving all primary and foreign keys and then generate the SQL Server script that you can then execute to create your SQL database--complete with primary keys, foreign keys, indexes and constraints you created on the Access side.
Problem solved. 🙂
In addition it will let you document your SQL Server schema, including notes that will be made into extended properties that SSMS can read--and that's a painless instant way to document your tables and columns! This is a GODSEND, trust me. Further, it will give you a tool to make future modifications to your SQL database--then create the scripts to add columns, tables, etc. All while letting you document it with pretty pictures and text comments accessible via SSMS.
It isn't free, but I swear to you it's like getting an assistant DBA of your very own.
Also, speaking of Godsend tools if I were you I'd SERIOUSLY bug your boss to buy Redgate's SQL Compare and SQL Data Compare. These let you update the schema of one database (say, QA or production) with the schema of another (say Development). Painlessly. Without forgetting anything.
Data compare lets you transfer data from one database to another, it's great for updating the dev database from either the QA or production databases. Again, not exactly cheap but they will pay for themselves really quickly.