M
Mr Newbie
I've just spent some considerable time putting together an application which
works pretty much OK. The issue I have around design is mainly concerned
with the Data Access layer.
Yes, we can pull data modify it etc, but the code required to do so is not
inconsequential, and the many functions one finds onself writing do mount
up.
All this is OK until you find you need to change a type or add or remove a
field, everything has to change and its a nightmare to have to retrofit your
code to remedy that.
So Im sitting here thinking that there must be a scalable flexible way to
approach the design to minimise this rework. Does anyone have any ideas,
URLS's etc that may be of help, or even a few words of advice.
Thanks Mr N
works pretty much OK. The issue I have around design is mainly concerned
with the Data Access layer.
Yes, we can pull data modify it etc, but the code required to do so is not
inconsequential, and the many functions one finds onself writing do mount
up.
All this is OK until you find you need to change a type or add or remove a
field, everything has to change and its a nightmare to have to retrofit your
code to remedy that.
So Im sitting here thinking that there must be a scalable flexible way to
approach the design to minimise this rework. Does anyone have any ideas,
URLS's etc that may be of help, or even a few words of advice.
Thanks Mr N