code conversion

[JohnE]

I have been asked to see if there is a code conversion tool that can convert
an Access app code to C#? I am posting here to see if any person in the
group has had to do such a thing when an Access app needs to progres to the
next step in its evolution. Have one that started in 1997 and has evolved
thru the different Access versions. It is using SQL for the backend (6gigs
in size) and there are about 40 - 50 people using the front end. I do
realize that any tool will not be able to convert it all, but would do the
majority.
Thanks.
John

 

[Tom van Stiphout]

On Mon, 12 Jan 2009 01:52:01 -0800, JohnE

Post back if you find one. I would be very cautious using it because
the two environments are so different it seems inconceivable that a
conversion tool would do a good job.

If you like you can migrate the application one chunk at a time, using
the Interop Forms Toolkit:
http://msdn.microsoft.com/en-us/vbasic/bb419144.aspx
This tool does not perform the upgrade, but enables an architecture
with a partial Access or VB6 app and a partial .NET app.

Another option is the VB6 upgrade wizard:
http://support.microsoft.com/kb/317885
but it cannot work with Access at all.

-Tom.
Microsoft Access MVP

 

[Mike Painter]

I have been asked to see if there is a code conversion tool that can
convert an Access app code to C#? I am posting here to see if any
person in the group has had to do such a thing when an Access app
needs to progres to the next step in its evolution. Have one that
started in 1997 and has evolved thru the different Access versions.
It is using SQL for the backend (6gigs in size) and there are about
40 - 50 people using the front end. I do realize that any tool will
not be able to convert it all, but would do the majority.
Thanks.
John

There have been a few Access to VBA attempts in the past which gave poor
results.
Ignoring all teh work that Access does in the background That's just moving
from one dialect to another.
Changing languages is a far greater problem and extends far beyond a
"simple" replacement of one style with another.

 

[Chris O'C via AccessMonster.com]

I've never seen a conversion tool to C# that saved the developer time. AAMOF
it can increase development time because of all the things it doesn't do
right.

What's the next step in this app's evolution? It has a SQL Server back end
so it has data integrity, data security, reliability, recoverability, speed
and scalability. It's already built. Why spend more money on it? Something
wrong with it? If there are problems, it's mostly because of poor design and
implementation or a slow network. These can be fixed faster and cheaper in
an existing app than by migrating to a whole new code base.

Chris