Access conversion to .NET

[sbowman@comcast.net]

I've seen a lot of tools out there that automatically convert Access
apps to .NET. If anyone has used one, I'd like to know which one and
what you thought of it. Are they really worth the money?

Thanks,
Shelley

[Norman Yuan]

Re: Access conversion to .NET

I never see one and I do not believe this kind of tool have broader use than
only possibly being usable to a very narrow types of application, if they do
exist.

No matter how good it claims, re-write/fix the code would be still
significant. Since more "conversion " is one time shot, if you could try it
and got good result, you probably would not need to buy it any more. So, if
they exist, you probably have to buy it first to try (to see if it worth the
money), but before buying it, you want to try to see the result...so, that
is a catch22. I'd not bother to waste time on this. Either stick with
Access, or do it .NET way and forget Acess completely.


<sbowman@comcas t.netwrote in message
news:1180037555 .351261.47010@p 47g2000hsd.goog legroups.com...

I've seen a lot of tools out there that automatically convert Access
apps to .NET. If anyone has used one, I'd like to know which one and
what you thought of it. Are they really worth the money?
>
Thanks,
Shelley
>

[PMK]

Re: Access conversion to .NET

Good answer from Norman, but I would add this:

Almost certainly there is going to be some cleanup, at a minimum,
involved. If the application is complex, contains a lot of VBA code,
or in particular has complex reports, for example reports with
calculations within them, then there could be really a lot of work to
do to clean up the conversion or conversion might not even be
possible. Crystal Reports is a lot different than the Access report
module.

So it seems to me the skills required to re-write the app are similar
to those required to clean up the 3rd party conversion. After all, the
database itself will just be converted to SQL Express or perhaps
simply separated into a back end Access DB and the .net app linked to
it - something that is easy to do manually. That leaves the front end.
If it is simple, and you have those skills, then why not just re-write
it yourself as the software is probably expensive? If it is complex,
then the software is unlikely to be able complete the conversion on
it's own and you will be stuck with a useless partial conversion.

Peter

On 24 May 2007 13:12:35 -0700, "sbowman@comcas t.net"
<sbowman@comcas t.netwrote:

>I've seen a lot of tools out there that automatically convert Access
>apps to .NET. If anyone has used one, I'd like to know which one and
>what you thought of it. Are they really worth the money?
>
>Thanks,
>Shelley