VB.NET conversion

A bit off topic but...
Converting an Access database to VB.NET keeping the same SQL Server
backend.
Crazy?
Windows Forms or Office Forms?
Any thoughts on this are appreciated.
lq

re: VB.NET conversion

Lauren Quantrell wrote:[color=blue]
> A bit off topic but...
> Converting an Access database to VB.NET keeping the same SQL Server
> backend.
> Crazy?[/color]

Well, if you're doing it for fun rather than profit, yes!
[color=blue]
> Windows Forms or Office Forms?[/color]

What do you mean "Office Forms"? .NET is either Windows or Web (at
least in the flavours I work in, which are .NET 2002 and 2003). If
you're converting an Access front end to a Windows front end, then you
need to have a keen eye on the business benefit, because it's a total
rewrite (though you can use the existing forms as design templates, and
the existing code as pseudo-code).

If you're converting to a Web app., then you've got a lot of work to do
(ASP.NET is a cool tool but it's NOT a RAD tool). However, both
flavours work very well with SQL Server, and there's a lot of help out
there in cyberland.

HTH

Edward

re: VB.NET conversion

thanks for that
lq