Data layer as a package

I am about to start a large project that will consists of many applications 
accessing various tables in a main MSSQL database.  The same application may 
be executed by several different users on a network at once.  A table 
containing something like company department definitions will be needed on 
more that one application and may have several users running applications 
that access that table.

Does it make sense to create a package with datamodules for these kind of 
tables?  For example, a datamodule would be created in the package to handle 
the department table.  Offering methods such as New(), Save() and Delete(); 
in addition this dm could contain a query listing all departments for use on 
a DataSource.

This would allow me to make a change to the package then recompile 
applications using that package...centralizing my data access layer in the 
package.  Is there a better way?

Thanks. 

You need to separate your business logic and data access into a separate 
application (App server) using something like RemObject DataAbtract, or 
Kwbm, or build something similar on your own.

Leonardo M. Ramé
http://leonardorame.blogspot.com