>>>I have a client that has been paying me to upgrade and maintain an MS Access application. I would like to convert it to .Net, but I would need some concrete reasons for justifying the cost. Now simply saying it's a better environment won't be sufficient.
>>>
>>>I'd be interested in hearing what you all think.
>>
>>Can you describe the features and functionality of the app? There would have to be an improvement or new feature added due to the upgrade to .net (IMHO) in order to justify it.
>
>
>- Developed in MS Access 2003
>- Allows users to gather customer's IT hardware info, then produces an Excel file which represents a quote for hardware support.
>- Changes are frequent. Small to largescale, with new features and bugfixes ongoing.
>- It's limited both in its design and in the fact that it's done in Access. The code is exposed to anyone who clicks the Database button on the toolbar.
>- New feature coming soon will require me to call into SQL 2005.
>- Althought its kludgy to work with the customer seems to be happy with it, but I think they just don't know any better
>- I'm currently working on a C# app for them, and I could combine both into one, which seems to me to be a better long-term solution

You might start by looking at msaccess developers' reasons for migrating to dotnet:

http://www.devcity.net/Articles/268/2/article.aspx

I would visit some msaccess developer forums.