I do this all the time. I get that you don't need a relationship here, but that is the best way to handle this. You can set it up in such a way that it isn't an issue. I have a table called "app settings". I created one record, Record ID#1, then took away my and everyone elses permissions to create new records for that table. It will always just have one record. Relate that table to your table (i'll call your table "jobs"). In the jobs table, find the foreign key, 'Related App Setting', and set the default value to 1. From that point onward, every job record will be related to the app setting record correctly. You can bring in child fields to your hearts delight. There are a lot of other things you can do with this kind of setup.
This is a great tip, and one I can see using going forward. You also made me realize that for unrelated reasons, shutting down access to add records on this table is something I absolutely needed to do regardless. It would have occurred to me eventually, but better sooner than later!
