TO ALL : A tip for a structure
Posted: Sat Jul 25, 2020 4:30 pm
the only solution I have found to solve the problem for the prices for the beach is to create a price for each day for all three seasons.
The problem is that the total number of fields has increased.
In the old school of programming (of thought) of the old clipper from the Autumn 86 - Summer 87 version passing through DBIII ,
my friends always advised me not to make an archive with many fields but to make many archives with few fields
and now I really don't know if this solution is decisive or I am wrong system.
With this solution I would solve the price problems because I have them entered directly by the end user.
the problem is that the archive now has 105 fields. and three indexes that will likely run slower
I'd like to know what you think about it
The problem is that the total number of fields has increased.
In the old school of programming (of thought) of the old clipper from the Autumn 86 - Summer 87 version passing through DBIII ,
my friends always advised me not to make an archive with many fields but to make many archives with few fields
and now I really don't know if this solution is decisive or I am wrong system.
With this solution I would solve the price problems because I have them entered directly by the end user.
the problem is that the archive now has 105 fields. and three indexes that will likely run slower
I'd like to know what you think about it