Recent content by BartBE

Solved it. Thanks to the kind of help of someone who has greater knowledge of VBA than I do. The solution, if anyone is interested: Turned the field "Anciënniteit" in the table WN_Terwerkstellingen into a dropdown field with limited values. (I don't know the exact name in English.) In the...

I just realized that the wage should not correspond to the most recent indexation. It should instead correspond to the indexation that was in effect at the starting date of the employment. This means I need to adjust my initial question: I need the wage that corresponds to the function's...

Indexation is indeed an effective date. The goal of this field is, like you say, to keep a history. Aside from the ID field, the table BAREMAS looks like this: INDEXATION - SCALE - SENIORITY - WAGE 1/7/2011 - A145 - 0 - 2000€ 1/7/2011 - A145 - 1 - 2025€ .... 1/7/2011 - B101 - 0 - 1500€ ...

Determining which wage is most recent is not really what I'm trying to do. It is only a part of it. Loon (wage) is determined by anciënniteit, indexatie and barema. An employee's function determines the barema. This is a fixed set of wages. The employee's years of service...

Bump. I have a test version of my database if that helps. (Attached) Do note that not all combinations of barema (scale), anciënniteit (seniority) and indexatie (indexation) have been included in the BAREMAS table. Can anyone help?

I read it and followed your advice up to the point of the naming prefixes. The reason for that is simple: my knowledge of VBA is very limited, which means I won't be using it :) I understand it must be difficult to understand a structure like that in a foreign language. Which is why I made a...

No worries :) BAREMANUMMERS contain the numbers we use to identify the salary scales. The scale an employee gets, depends on the job he has. (Hence the field "barema" in the table "functies", which contains all relevant job information.) ANCIENNITEITEN contains numbers from 0 to 25. These...

I have edited my OP to avoid this misunderstanding. So, does anyone have an idea on how I can get the standard value I want?

Now I understand where your question is coming from :) I should have put it more clearly. Sorry for the confusion - explaining this in a foreign language does not make it easier for me :) Anyway, it is in fact one form. Using the navigation bar at the bottom of it, we browse the records of the...

Yes. There are several subforms on it, like the one based on WN_Tewerkstellingen. This way, we have all the information on an employee in one place. It also works great to make individual changes. I have other forms for changes that happen to groups of employees.

Thanks for the advice. I fixed it in the table Baremas. It now has a singular primary key: an autonumber field called "ID". To ensure every combination of indexation, scale and seniority are unique (which is why I made that combination of fields the primary key), I have installed an index...

One form per employee. The link between the main form (based on WN_Persoonsgegevens) and the subform (based on WN_Tewerkstellingen) is Rijksregisternummer (employee ID). The idea behind that is to see the employment history of every employee.

Hello, Attached to this post, you will find (the relevant part of) my table structure. It's in Dutch, so I will try to explain what the relevant fields are about. The table BAREMAS contains all the wages we pay. The wage an employee gets depends on three variables: indexatie, barema and...

Jzwp22, It works now. Thank very much for all your help! I am going to look into learning about VBA. It looks interesting. EDIT: It just occurred to me I never looked into this. Are you referring to the record source property of the form (translated)? That is indeed empty now.

Thank you very much! Works like a charm. I understand this problem couldn't have been solved in the standard Access environment? I guess I need to start looking for a training myself :) I really didn't expect to get my work done for me, which is why I'm reluctant to ask for your help one more...