William Hindman
wdhindman at dejpolsystems.com
Sat Feb 21 00:41:38 CST 2009
Dan ...first time out you will have a significant learning curve ...plus outlays of money and time for tools and resources necessary to dupe what Access does by its lonesome ...time to build your own code library ...time to learn which web resources know what they are doing and which don't (too damn many of those) ...and looking for a replacement for AccessD which there isn't even as much as dba-vb tries (maybe you can help) ...and you will spend a lot more time getting a prototype to work. ...depends on how much of that cost you can absorb and how much you want to charge the client for ...my rough guess would be a minimum of 2.5 x the same app in Access ...but that's me and my apps and there are a LOT of things you could run into that will take you days to figure out ...things that are givens in Access or simply don't exist in the .net world. ...but then you learn classes and inheritance and you start to figure out that .net has one heck of a lot of more stuff already built in than access if you just know how to find and use it ...and then you find yourself doing things you never thought possible ...and your next .net app is a lot easier and quicker to produce ...and a lot more fun. ...I'm working in access again now because that's what the client wants ...I find it ...um ...stodgy ...for lack of a better word ...what it does, it does pretty well and I've built a nice gui over the years so it doesn't look like access ...but if you can get over that first hump, you'll find that .net and visual studio are awesome by comparison. ...btw ...don't just assume that vb.net is the right tool for you ...its not vba and the syntax is deceptively different ...I spent a lot of time in vb.net before I swallowed hard and started playing with c#.net because, among other reasons, the quality and quantity of .net code resources in c# is much higher than it is in vb ...if you take the work, sign up for the dba-vb list ...gustav and shamil are already there waiting. ...hth William -------------------------------------------------- From: "Dan Waters" <dwaters at usinternet.com> Sent: Friday, February 20, 2009 2:54 PM To: "'Access Developers discussion and problem solving'" <accessd at databaseadvisors.com>; "'Discussion concerning Visual Basic and related programming issues.'" <dba-vb at databaseadvisors.com> Subject: [AccessD] Conversion Time: Access to VB.Net (cross-posted) > Does anyone have any rough estimates on converting an Access FE to a > VB.Net > FE? I know this depends on many factors, but a client has asked me to > provide a rough estimate today. I have just begun learning this, so I > don't > know yet. > > Any thoughts? > > Thanks! > Dan > > > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com >