Re: Data modeling for a multi-company product

On Jan 24, 11:32 am, "DBMS_Plumber" <paul_geoffrey_br..._at_yahoo.com> wrote:
> On Jan 24, 8:05 am, Bob Badour <bbad..._at_pei.sympatico.ca> wrote:
>
> >To amplify Kevin's reply, most ERP software re-implements a majority of
> > the functions of a dbms while ignoring those same functions when already
> > supplied to them by the dbms. To extend Bob's observation, qualify the verb 're-implements' with the
> adverb, 'badly'.

So what you would do differently if you ran software company writing software for multiple companies to deploy, with a business requirement to ensure that you not be locked into a single OS or DBMS would be what?

And for the original question, if, additionally, you needed to be competitive by providing features such as the ability for each customer site to identify which attributes would be required for data entry for each such data collection mechanism (e.g. screen) would you design nullable attributes into your logical data model? Thanks for any clues on either question. --dawn Received on Wed Jan 24 2007 - 21:57:18 CET