Normally this is the case, and you are right about this. Our team here works on supporting Trimble field and office solutions for users and we don't always have the luxury of having a .GGF already accessible, as users create their own or naming conventions change over time. For everything that calls a default code we don't have an issue with, its when we hit custom ones that don't already exist it would be good to have the ability for TBC to reference the one that has been copied with the job.
The .GGF is there and it has been copied from Access so TBC should give users the option to reference the relevant file in the import or simply use it, rather than tell the user it doesn't have it and then get them to go off and sort out its import and use. It doesn't help either that the .GGF can't be dragged and dropped into TBC to reference it either.
Its not a deal breaker by any means, just something that seems a little clunky for anyone that would hit that menu.