Jump to content
Server Maintenance This Week. ×

self related calcs


This topic is 8548 days old. Please don't post here. Open a new topic instead.

Recommended Posts

It's kind of a game of numbers. Let's use as an example an inventory system in which available quantity is calculated on the fly by adding all the + and - inventory transactions (instead of keeping a single number). This is a good general approach (transactions,that is) which allows entry errors to be discovered at a later date. If the inventory quantity available is just altered, you don't know how you got there.

The downside of this approach is that all these transactions must be processed to display an inventory quantity for an item. Looking at a single item, this might be ok for limited numbers of transactions. If you are either looking at items with a lot of transactions or a lot of items, this can drag to a crawl in displaying a list view. In most inventory systems this is too slow. A middle ground is usually to update a "working" quantity each night. This working number is debited or credited for real time transactions and updated by doing a complete processing of transactions each night.

Bottom line: in smaller solutions (records, number of related calculate field) this may be ok. In larger application it can easily be too slow. -bd

Link to comment
Share on other sites

This topic is 8548 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.