Average cost to convert Access97 DB to .NET Application

dakota97

Centurion
Joined
Nov 14, 2003
Messages
116
Location
Pennsylvania
Hi all,

Can anyone give me an idea of what the going rate for converting an Access 97 Database, with a user interface, modules, etc. to a working .Net application would be?

The reason I'm asking is b/c I'm doing some sub-contracting work for a company, and right now their whole accounting package is comprised of a database that was written over the years as different needs arose. The DB is decently complex from what I can see. However, the main issue that I see could potentially be a problem is that their server is in desperate need of an upgrade, and they've had issues with viruses and corrupted files. The way the DB works is that there are 2 copies (one on the server and one on the user's machine) and the tables are linked from one to the other. With an average of 4-7 people working in the DB at one time, and each having a seperate copy open, it seems to me that:

1.) The network is going to significantly slow down
2.) The DB could potentially be corrupted if one of the user's machines has issues

Any input would be greatly appreciated, as they have also mentioned the possibility of purchasing a software package that does everything that this DB does. However, there again, I don't think they're going to be able to find a package to meet every need, or they're going to be spending a lot more than if I would convert everything myself.

What do you think?

Chris
 
It really depends how many hours worth of work it will take you..

At the moment i am charging £25 ($45) per hour for contracting work, but it depends upon your skills and experience. A colleague of mine charges twice what i do, but then he's been doing it an although lot longer!

An 18 yr old school leaver would be lucky to get £8 per hour, personally i have a university education and 1 yrs worth of commercial experience. If i had another 5 years experience i would be chargin about £40 per hour.
 
I recently took on a project exactly like this (converting a Microsoft Access 97 database with a forms-based interface to Microsoft Access 2002 with a .NET interface; and no, Microsoft Access 2002 wasn't my idea).

The only advice I can offer you is this: unless you want to become suicidal, stay away from these projects like the plague. Tell them to buy a commercial solution, or pass the project off to someone else. Even at $150/hour it wouldn't be worth it, especially if the database is corrupted (as it was in my case).
 
Back
Top