[AccessD] Unifying Data

Susan,

I respectively have to disagree with you.  Unless either App A or App B
is a personnel app, then they both should draw their employee data from
a database that holds the employee data.  If even small amounts of
employee data are stored in two different apps, they can get out of
sync, the old inconsistent data problem of poor database design.

Charles Wortz
Software Development Division
Texas Education Agency
1701 N. Congress Ave
Austin, TX 78701-1494
512-463-9493
CWortz at tea.state.tx.us
(SELECT * FROM users WHERE clue > 0)


-----Original Message-----
From: Susan Harkins [mailto:harkins at iglou.com] 
Sent: Thursday 2003 Feb 20 09:20
To: accessd at databaseadvisors.com
Subject: Re: [AccessD] Unifying Data

Only if there are a lot of employees and a lot of updates -- wouldn't be
worth it.

Susan H.


> Two apps
>
> App A Application B
>
> Both apps contain employee data.
>
> Rather than maintain two sets of the same data in both apps how would 
> you handle it? Export the employee data and anyother common data (if 
> possible) out to App C and manage that via a different interface?
>
> Comments
>
> Martin WP Reid
> Information Services
> Queens University Belfast
>
> Tel: (02890) 273750