Hm, now i think a little bit more about it, it is actually very logical. because the Calendar acts as a Link Table in this case so it makes the values available.
You are right. your date field is making an association between multiple tables.
Now if you select any value for another field in a table then the corresponding value of other fields from other table based on the date selected will only appear. In your case if you do not want to associate multiple tables based on date field then you need to change it in your script and update the data model.
One quick question. Are the date field in Omzet, Ranges and Uren table different date.
I mean are they like one is order date then another is shipment date. If the date represents two or more different fields then better to keep it separate and create master calendar based on the date which you want the end user to use as filter selection.
The idea is to have a two-column table between the calendar and the other three tables, the first containing a date (linking to the master calendar) and the second a Generic Key, like in the following
GenericBridge:
Load Date, 'Date:' & Date as %Date Resident xxx ; // Linking to Omzet and Ranges
Load Date, 'YearWeek:' & YearWeek as %Date Resident yyy; // Linking to Uren
And then define the corresponding %Date field in Omzet, Ranges and Uren.
.png "Former Employee"){kind=icon}