skfbelgium

Hello, I'm trying to follow the guidelines to create a separate file for the UI layer. But I don't know how I should implement the valuelists: I have a table with projects and a table with project statuses. Some of the statuses are marked active. Now I need a valuelist of the projects with statuses defined as active. In the separate UI file, I reference to the projects database, define a relation between the projects and statuses. I've created a table in the UI file (Active projects) with one global field 'active' and define a relationship with Project_status. Now I would like to have a valuelist with the active projects in it. But when I restrict the valuelist to "active projects", the valuelist remains empty. Thank you for your feedback!

Thanks a lot! It is an old fm database (+10 yrs), so it still consists of multiple files. Maybe we should think of integrating it more.

I have a table with people which can be active or inactive. I managed to populate a value list of the active people using a self-join on a global field set to "active". I need to reuse this value list in other files, multiple times. Is it correct that the value list remains empty unless I recreate the self-join relationship in every file I need to use the value list? Thank you for your feedback!

I'm almost there, but not completely. How do I need to link the Projects table with the Types table? Only with the ProjectsID or also with TypeID? If not, how can a layout in Projects know which transactiontype I want to summarize?

Hello, Yes, I need to have them in a browse layout. Can you elaborate on the "in between" table? I'm not sure if I understand it correctly. The new table Types is able to carry over all the ProjectIDs to the Transactions table? It sounds cool if this works, I'll give it a try, thanks!

Hold on, I have 12 transaction types (3x4). So I need to create 12 fields in the project table each with a constant value in so I can define the 12 relationships? Each relationship links one of the 12 fields with a calculated field in the transaction table. And I can use a sum on the project table to calculate the sum. I had a problem with the fact that I needed to create 12 fields in my project table to define these relationships. So all records in my project table end up having the same 12 fields. I thought I missed something so I could avoid this.

You're absolutely right, it is straight forward. It is awkward how one can miss these things. Thanks!!

Hi, I'm clueless in finding a solution for the following common issue: I have one table with all sort of financial transactions (e.g. incoming, outgoing, from subcontractors, ...) with different statuses (draft, in progress, done). I have a second table with projects in it. I would like to include in the projects table the summary of the related financial transactions: e.g. for project X, - show the sum of all incoming transactions with status done; - show the sum of all incoming transactions with status in progress; - ... Do I need to create a seperate relationship for each sum I need or do I need to use a script for this? I appreciate your help!