"Norman Yuan" wrote:

> If the Access application is in *.MDE, there is nothing you can do: the VBA
> code is not available at all.
>
> There are some conversion software claiming to be able to convert Access app
> to VB exe, or even .NET (VB.NET or C#) exe. I do not believe them, unless
> your Access app is extremely simple. Access app and .NET app are just too
> different to be converted. You can search the net and buy one or more
> so-claimed softwre and try (I wouldn't waste time and money on this,
> though). At best, you still need some manual fix. Using VSNET? the
> converting condition is "Good .NET skill" + " Manual re-write". No other
> way.
>
>
> "Morten" <Morten@discussions.microsoft.com> wrote in message
> news:0B711B0F-B0A7-4019-ABCE-85972B7ACB07@microsoft.com...
> > Norman,
> >
> > My original question was a little short so let me refrase. My Access XP
> > (2002) system includes a large amount of VBA code. Is it possible to
> convert
> > the system from a .MDE to a .EXE VB application using VSNET?
> >
> > RGDS
> > Morten
> >
> > "Norman Yuan" wrote:
> >
> > > If .Net_Skill="Fairly Good" Then
> > > If "Port"=="Manually Re-write" Then
> > > Answer="Yes"
> > > Else
> > > Answer="Almost No"
> > > End If
> > > Else
> > > Answer="Forget It"
> > > End If
> > >
> > > "Morten" <Morten@discussions.microsoft.com> wrote in message
> > > news:E75BCEDF-5E8C-4311-B908-E79DAD0B40A5@microsoft.com...
> > > > I have a major MS Access database with lost of forms, report code etc.
> Is
> > > it
> > > > possible to port this to .Net without too much trouble?
> > >
> > >
> > >
>
>