How many flowfields in a single table?

kirkostas

I want to create flowfields in table Job for each field on this form 1025 Job Statistics.
All these fields will be shown in a page Job List and some of them will be ratio extended data type.
Is this going to affect a lot the performance of the system?
Is it possible to achieve this? Because we are talking about 40 flowfields.
Do you have any other suggestion?

pdj

kirkostas wrote:

Is this going to affect a lot the performance of the system?

Yes... You will regret it, if you go this way. (Except if you also sell hardware 8))

kirkostas

pdj wrote:

kirkostas wrote:

Is this going to affect a lot the performance of the system?

Yes... You will regret it, if you go this way. (Except if you also sell hardware 8))

What do you suggest?

DenSter

I would suggest not to add the fields to the table, and to provide a statistics screen that you can open from the list page.

matttrax

You need to approach it from the business side first. What fields do they need to see all of the time, and what fields do they need easy access to. If they need to see it all the time, FlowFields are good. If they need to easy access, the Statistics form is good. Obviously each needs to be balanced with performance (for when they come back and say we always need to see every field at all times )

DenSter

Adding 40 flowfields to a list form is only a good idea if the users don't mind waiting for individual records to pop into the form, this is always going to cause big performance issues.

Another idea might be to add a handful of the most important ones to a factbox, which then would only load for the active record.

kirkostas

I thank you all for your ideas.