lsamberg

I created a solution for a client. The solution took a pile of their data and with a bunch of scripts, etc. produced analyses and reports. They liked it and wanted me to do the same thing with a different dataset. So I duplicated the database file, deleted all of the records and imported the new dataset (from a spreadsheet). Rinse and repeat. I now have four different files with four different datasets. Everything works great, but the problem is that every time I fix or add something in a script, I have to do it four times. This is cumbersome and error prone. So maybe I didn't approach this correctly. Is there a better way?

Well I don;t know if this is the most elegant way to do it, but I tried it and it works. In the main database create a global field that contains the string "ActiveNew". In the subsidiary database create a computed field that concatenates the two fields. Create the relationship so that it includes both the Key between the records AND a link between the global field and the computed field. Then in the main database you can create a computed field like (if (count(sub::any-field)>0, "Yes", "No"))