Linked Database - Best Way to Reuse Employee/HR Database

[JMongi]

So, as you might expect I'm repeatedly using a list of employees for the various databases I'm creating. I figure I ought to create a master HR database since it's likely I"ll create something like that in the future anyway. Is there a preferred method for pulling up-to-date data into my other various databases from this master HR database? Is creating an external link that's refreshed upon opening the main way? Are there any gotchas?

 

[theDBguy]

Hi. I was thinking maybe just link the other databases to the master database?

 

[Ranman256]

yes, all 'common' tables: employees, vaca ,etc
should all be linked from the HR db to all company apps (db)

 

[JMongi]

Ok. I know it seems simple enough. I just wanted to make sure there wasn't an extra little wrinkle to make it more robust or plan for a future more complex system. Thanks!

 

[Pat Hartman]

The robust method is to store data in one and only one table. You can make multiple BE databases if you need to but remember, you can only enforce RI within any single database. Therefore, I would not at this time create multiple BE's. By the time you get to that, hopefully, you will have moved to SQL Server and so the issue will be moot. Everything can live in a single database.

 

[JMongi]

Thanks for the replies! After doing a bit more research/reading, the alternatives to the one database idea apply more at the enterprise level than at my level. As Pat mentioned, not really a thing to worry about at the MS Access level.