MS Access best practices -- at what point do YOU decide to split an application into multiple frontends / backends
Posted on 2015-01-14
Let's be clear.
I am not talking about splitting an mdb file into front-ends and back-ends.
That was done long ago, and the back-end is on SQL Server.
What I am talking about is when and why you have looked at a massive, monolithic app and said
'Hmm, it's time to break this puppy up into a bunch of different applications because its HUGE!'
I'm beginning to go north of 150 forms and 150 reports.
Eventually, I may hit the ~1000 limit for the number of permitted modules.
All the data hangs together and relates -- it's just that, like any well-designed database app, it tends to subsume every business function it comes across.
You get an application going that tracks the central business activity, customers and employees, and soon every data-centric activity has strong relations with the app--and the app gets extended, and extended, and extended...
How and when did you say 'stop' and begin to break functions out into separate applications?