Solved: Creating a table for manually input values in FM

[ccbarbeau]

Morning all,

I'm working on a report where each cell is a singleton. There are several (about 45 or so) that need to be calculated fields that use values that are unique to each field (ie, sales January 2010 for entity XYZ, sales Feb 2010 for entity MNO, etc).

I'm asking myself whether I can create a table in FM where I could input all my data and reference the field in my query calculation. It would make it so much more time efficient than changing each value in each singleton every time the denominator changes!

Any help is greatly appreciated.

Have a great day!

CC

[blom0344]

For singletons this could work (no chance cross-joins occur), but you would need to maintenance tool to update the reference table (unless you allow direct database access) You would also need to add a unique code column to the table to be able to select (= filter) each required value per singleton..

[ccbarbeau]

That makes sense. Now let me ask you my 'it's Friday and my brain is jell-o' question: how does one go about creating said reference table? Do I create and import? Or can I create in FM?

[blom0344]

Create and import would be the logical choice. However, you could probably write a SQL query subject that substitutes a database view, but this would be messy.
However creating a additional table will be a breeze. Maintaining the data is another issue..

[ccbarbeau]

I see your point. Messiness is a bad thing.

Regarding maintenance, I plan to upload a reference table once each year. Shouldn't be too bad, considering I'm also the only one using the development here.

If I may, what format would you prefer for importing?

Thanks again and have a great weekend,

CC

[blom0344]

I see your point. Messiness is a bad thing.

Regarding maintenance, I plan to upload a reference table once each year. Shouldn't be too bad, considering I'm also the only one using the development here.

If I may, what format would you prefer for importing?

Thanks again and have a great weekend,

CC

I use .csv for importing into SQL server