[AccessD] Access Application - per unit cost

Barb,

I'd have a talk with your client and thoroughly discuss the decisions that
he wants to make with the 'unit cost' number.  I'll bet that he really needs
something other than 'unit cost'.

Best of Luck,
Dan
 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Barbara Ryan
Sent: Wednesday, April 05, 2006 11:11 AM
To: Access List
Subject: [AccessD] Access Application - per unit cost

I have been working on an Access application for several years.  My client
has asked for a "per unit cost" for the development of this application,
although he is unsure what "unit" is most meaningful (e.g., database object,
lines of code, etc.).

The database functions vary tremendously in their complexity --- e.g., some
reports are very simple while others contain several subreports, and/or
output spreadsheets or files.  The database contains lots of VBA code.

Are there any white papers, etc. that address this issue?  In your opinion,
what is the best method of computing a "per unit cost"?

Thanks,
Barb Ryan
-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com