Should I create a new related "file" or a related "table" within the same file?
I'd say keep the tables in the same file, unless you have a good reason not to. See here for some good reasons.
Would I be correct in thinking that if I go the related table method that I won't be able to create access restrictions for the original "Products" file whilst allowing acces to the "Sales" area.
I don't think that is correct - but I am not sure I understood fully what you mean.
Thanks, one of the reasons I asked the question was in the post you kindly created a link for
"sets of tables that create separate modules that may have different access privilege sets"
I was thinking that if I needed to restrict acces for some staff to the "Products" file which has confidential pricing information. Then the "Sales" file/table would need to be a seperate "file" to create these access privilages.
Or is it possible to create access privilages for individual "tables" within the same file.
You can certainly allow/deny access to specific tables in a file when defining a privilege set.
Excellent..... thank you