Upsizing (Myself) to VB.net

[TKnight]

Hi,

I would just like some general opinions about progressing from developing in Access/VBA to developing in VB.net?

Basically I am a self taught developer. I started learning VBA by recording Macros in Excel and looking up the code afterwards. I then started building more and more complex DBs and now write full applications with Access F/Es and SQL B/E (if the size requires it). The problem is I feel that because I only develop in Access my earning potential is limited because people regard me as a 2nd (or 3rd!) rate developer. It's weird but I can't help but feel that if I developed the same type of systems in something like .net I would probably double my salary!

Has anyone gone from pure access/VBA development to .net? If so what is the learning curve like? Is it likely I will be able to pick up a book and get to grips with it in a few months?

Any opinions would be really appreciated.

Thanks,

Tom

 

[Dennisk]

I have grone from Access to .net and at the age of 58 it was/is a nightmare. However after a year I am getting more comfortable with it.

The big problem was data aware classes (ADO.NET). If you 'drag and drop' from the tool box, 100s of line of code are generated for you. Then if you want to start over and start deleting the classes you end up with a corrupted form that cannot be opened to fix. So I develop all my classes in code.

 

[HiArt]

I have done it too, but more from an Excel VBA route.

vb.net /= VBA. There are many simularities, and a fair few things will trip you up big style.

The great news is "Google". I search "vb.net xxxx" to find how to do almost anything! Then there are forums to help out if you get really stuck! I never had to refer to a book, there is a lot of free help out there. Perhaps my code breaks all sorts of faux pahs, but who cares if it works?

The main problem I find is switching between the two. There are neat things in Visual Studio IDE I wish was in VBA IDE.

However, I found the learning curve not very steep and was able to bash out some neat applications after a few weeks.

 

[Banana]

Just so everyone know, you can consume .NET components within Access/VBA. That way you get the best of both worlds if necessary.

I personally like Visual Studio IDE, but it doesn't change the fact that Access takes less time to develop, and will solve 90% of business problems re-using solutions already used in past (and can be found via google). It's that 10% where the requirement are too stringent or detailed that it breaks Access's assumptions with what you want to do with your data; that is where I would turn to .NET to supplement the Access's ability.

HTH.