how $ much $ for a Custom Access Database?

W

WebDude

Good evening,


I have been donating my time
for the past 6 months
developing a ms access database
for a department in the canadian government.
BUT
now im wondering if i have been spending
too much time And maybe i should recommend
that they hire an actual professional
to finish the database (or design a new one).

So im wondering, how much do you guys
charge for a custom ms access database?


I cant charge my boss for the work ive done,
cause im a volunteer, but at least i could give
him some idea of what it might cost him
to hire someone else.. someone else
that will do it right!

Cheers,
WebDude Out.
 
J

John Vinson

Good evening,


I have been donating my time
for the past 6 months
developing a ms access database
for a department in the canadian government.
BUT
now im wondering if i have been spending
too much time And maybe i should recommend
that they hire an actual professional
to finish the database (or design a new one).

So im wondering, how much do you guys
charge for a custom ms access database?

How long is a piece of rope?
and for that matter, how good is the rope?

Most developers charge by the hour, ususally with estimates. Hourly
rates vary greatly depending on the skill of the developer, their
region, and what the market (and the customer) will bear; I've seen
rates posted here from $15/hour to $200/hour, with $60-80 being
perhaps a common range. The hours needed would of course depend
greatly on what needs to be done: a VERY rough rule of thumb might be
45 minutes per table, 1 hour 30 minutes for a complex form, 30 minutes
for a simple one, etc. - but that will of course vary.

I've done databases for $200 (well, I've done databases for free, but
that's a special case); I've done longterm collaborative developments
for a great deal more than that as well.


John W. Vinson[MVP]
 
L

Larry Linson

John Vinson said:
How long is a piece of rope?
and for that matter, how good is the rope? . . .
The hours needed would of course depend
greatly on what needs to be done: a VERY
rough rule of thumb might be 45 minutes per
table, 1 hour 30 minutes for a complex form,
30 minutes for a simple one, etc. - but that
will of course vary.

Ah, John, you are a brave fellow to offer even a "rough rule of thumb".
<GRIN>

I think you covered it very well in the two parts that say "The hours needed
would of course depend greatly on what needs to be done" and "but that will
of course vary." And, in the qualifications stating factors influencing
rates.

Larry
 
W

WebDude

John,

Hmm.. my database is similar to the NorthWind database. So then, how much
would you charge to do something like the NorthWind database (which has..)

8 tables
13 reports
15 saved queries
21 forms
...some macros and modules



Cheers,
WebDude.
 
J

John Vinson

John,

Hmm.. my database is similar to the NorthWind database. So then, how much
would you charge to do something like the NorthWind database (which has..)

8 tables
13 reports
15 saved queries
21 forms
..some macros and modules

I'd prefer not to discuss terms in this public forum. If you're
seriously interested in exploring the issue, email me at jvinson <at>
wysard of info <dot> com and indicate your budget and timeframe.


John W. Vinson[MVP]
 
D

Danny J. Lesandrini

Between $5,000 and $10,000

(But my mamma told me never to quote fixed bids!)
 
J

John Gray

"WebDude" wrote...
[...][...]


...
[...]
a VERY rough rule of thumb might be 45 minutes per table,
1 hour 30 minutes for a complex form, 30 minutes
for a simple one, etc. - but that will of course vary.
[...]


It's a bit late for this thread, but I wanted to add another $.02 ;-)

In addition to John V's time-per-object idea, it can be useful
to break the project down into stages/aspects of development
(and break each stage down further, as needed).

Something like...
- gather info
(requirements - details of what the application is supposed to do)
- design/test db structure
(entities and relationships)
- design/test visual interface
(data entry, lookups, navigation through forms)
- design/test import routines
(if applicable)
- design/test export routines
(if applicable)
- design/test reports
(feed data back out in useful format)
- documentation
(for self and client)

Doing this kind of thing can also help make a seemingly *large* project more manageable.


John
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top