Hi All,

Thanks for the replies. We had similar doubts and that's why this was
posted.

Ours is a payroll application and this table stores the processed
details of all months. In our design, there are user definable salary
components. There can be 20 to 100 components typically (including
statutory, intermediate components). Now there are 9 values attached
to each component (original, Loss of pay, arrears, net value etc).
So, in the worst case, there can be 900 values against each staff (I
put 2000 to 3000 on the higher side). Table also contains few other
fields.

In our existing design, we store the info staff & component wise.
There is no problem except that certain report takes lot of time (as
info has to be unpacked every time). I feel the most natural way to
store this info is, to store the complete data staff wise, but then
you will have more columns.

What we wanted to know is, when a Database system supports unlimited
columns, are there any problems related to it?

With regards,
Niegil

--- In firebird-support@yahoogroups.com, "guillemvic"
<guillemvicens@...> wrote:

>
> --- In firebird-support@yahoogroups.com, "niegil_firebirddev"
> <niegil.thomas@> wrote:
> >
> > Hi All,
> >
> >
> > I have a requirement where my table needs around 2000 to 3000
>
> I must say I agree with Martijn. I have never seen a table that

needed

> more than 25 columns but once, and then I already thought about ways
> to minimize the columns number...
>
> You should reconsider your design. Also no offense meant :-)
>
> Best regards,
>
> Guillem
>