I guess I've reached that tipping point where a main app is singing and dancing with a growing amount of parameterisation.
Most businesses have in common 1. Accounting 2. collectibles and receivables ,, ordering in/out ,, various ways of billing, invoicing ---all of which keep developing, to most clients benefit.
Then it comes to types of operations that are specific to certain clients that if included and hidden for others will just bloat. Example a pretty big development is underway for CIT (Cash in transit) through internal teller banking and redirverted after counting to clients' banks. Too much to tag onto a comprehensive application without separating and freezing that development. Difficult for future bug fixes and enhancements having to be duplicated multiple times.
I would love to have a little discussion around this
The solution is probably using, in combination;-
A. The standalone specialised apps (.ADB) - with their specific menus and functions etc
B. Placing all of the Main apps generic scripts and functions into a Library that can be shared
C. Switching between "apps" (main app to specialised sub app) seamlessly for specified clients.
I know for example Peter, Stan, Mike, Tom, Ira and a number of others in similar environment, have mentioned various parts of the above.
Any pitfalls to watch out for ?
What recommended way to
- switch between apps and
- maintain common scripts/udfs/menus separately?
Most businesses have in common 1. Accounting 2. collectibles and receivables ,, ordering in/out ,, various ways of billing, invoicing ---all of which keep developing, to most clients benefit.
Then it comes to types of operations that are specific to certain clients that if included and hidden for others will just bloat. Example a pretty big development is underway for CIT (Cash in transit) through internal teller banking and redirverted after counting to clients' banks. Too much to tag onto a comprehensive application without separating and freezing that development. Difficult for future bug fixes and enhancements having to be duplicated multiple times.
I would love to have a little discussion around this
The solution is probably using, in combination;-
A. The standalone specialised apps (.ADB) - with their specific menus and functions etc
B. Placing all of the Main apps generic scripts and functions into a Library that can be shared
C. Switching between "apps" (main app to specialised sub app) seamlessly for specified clients.
I know for example Peter, Stan, Mike, Tom, Ira and a number of others in similar environment, have mentioned various parts of the above.
Any pitfalls to watch out for ?
What recommended way to
- switch between apps and
- maintain common scripts/udfs/menus separately?