Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Best Practice - Internal Code field for Heirarchial tabl
Message
De
06/09/2004 23:45:09
Dragan Nedeljkovich (En ligne)
Now officially retired
Zrenjanin, Serbia
 
 
À
06/09/2004 16:05:40
Information générale
Forum:
Visual FoxPro
Catégorie:
Autre
Divers
Thread ID:
00937935
Message ID:
00939837
Vues:
21
>Bhavbhuti, for accounts you don't need a separate hierarchical method as the number itself has the hierarchy. If you add another hierachical layer then you are complicating the problem.
>In fact sometimes it can be a pain when the accounting tree grows, as each level is capable of only 10 sublevels. If you don't plan well it can limit you (I have about 15 years in accounting experience); you can rewrite the tree, but it breaks backward compatibility (something many accountants don't care about because they break the books every year).

They do restart the books, but they don't have to restart the accounts. I've taught my customers' accountants to keep the accounts to the detail (except those they wanted to change), because then they get the automatic rollover, i.e. initial state from the previous year, plus a long term history for each account, because I've enabled the "peek into previous years". They loved it... and thought twice before being inventive with their account scheme. But when they learned how to use it, they saw what a powerful tool they got.

And this was more than a dozen years ago.

back to same old

the first online autobiography, unfinished by design
What, me reckless? I'm full of recks!
Balkans, eh? Count them.
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform