I understand that QV automatically connects all tables that use identical field names. Unfortunately, for a specific task I'd need to use identical field names in two different tables, which are not and shall not be connected to each other. Connecting them would result in circular references.

Is there any chance to use the same field name at two different tables and prevent QV from connecting them?

Reason for identical field names is that I use Multiboxes as central elements in my application. See the screenshot below. Multiboxes can only list fields. Users select price categories "low price", "mid price" and "high price". Those categories are used both in retail sales and label accounting; two totally different departments which mustn't be connected to each other.

If those two tables can't be kept separate, this would mean to add "pricing sales" and "pricing LA" as two separate elements in my multiboxes, which is kinda annoying in terms of useability.

You want two different fields shown as one? It is quite a different story.

First, that means that they are logically connected. The question is about the appropriate data model.

Second, it is possible to implement even if you have a reason to keep them separately. For example, in addition to pricing sales" and "pricing LA", you can create field "Pricing" as a logical data island to use it in multibox. Selection in "Pricing" can be copied into the "real" pricing fields by a macro. Or, use conditions and/or set analysis expresions to enforce the deiserd behavior, e.g.

Second, it is possible to implement even if you have a reason to keep them separately. For example, in addition to pricing sales" and "pricing LA", you can create field "Pricing" as a logical data island to use it in multibox. Selection in "Pricing" can be copied into the "real" pricing fields by a macro.