By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
454,968 Members | 1,247 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 454,968 IT Pros & Developers. It's quick & easy.

VB.NET conversion

P: n/a
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

Nov 13 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a

Lauren Quantrell wrote:
A bit off topic but...
Converting an Access database to VB.NET keeping the same SQL Server
backend.
Crazy?
Well, if you're doing it for fun rather than profit, yes!
Windows Forms or Office Forms?


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

Nov 13 '05 #2

P: n/a
thanks for that
lq

Nov 13 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.