A family of Microsoft relational database management systems designed for ease of use.
You want to create a concatenated column in a table to serve as a foreign key? Seems a bit unusual to say the least. How about you just use two fields for the foreign key as the usually the way it's done? Millions of tables in databases use a composite Primary Key and composite Foreign Key. I'm not saying that is the "only" way to do it, but if something has worked successfully for a very long time for a huge number of people, it's a good indication that it is the "most effective" way to do it.
I found one reference suggesting you can use a persisted concatenated column for a foreign key IF it is indexed, but then the Primary Key in the other table would also have to be the same concatenation of columns and also indexed.
I once heard an extremely useful analogy about using Access. It goes like this.
Using Access is somewhat like taking a canoe trip on a swift moving river. However, if you want to go upstream against the current, you'll be paddling hard all the time to make progress. If you go downstream with the current, you only need to use the paddle to make course corrections.
If you insist on "paddling upstream" by using concatenated primary and foreign keys, expect to invest a lot more of YOUR time in doing it.