Hi Bastien, Bastien wrote: > thanks for the patch. > > I wonder if we should trigger an error instead -- why a message?
Because it's not an error... When a reference (I guess it always must be an ID, then) is not found locally, Org will search for it in external known files. The problem is you see hundreds of messages "Finding ID location...", and you don't know which reference Org is trying to find... When you have multiple tables, with multiple references, this is a nightmare to find which was is wrong. Just use `TBLNAME' instead of `tblname' for the referenced table (or the inverse, if you apply the patch you sent me a couple of days ago), and you'll understand that it's good to know what Org is searching for. > (I don't like using sit-for, it's often worse than getting an error...) I don't like it that much either, but, here, it's the only way to see the message before being flooded by the "Finding ID location..." messages. Best regards, Seb -- Sebastien Vauban
