Switching from Access to Visual Basic

[ycim]

I have several applications written in Access, with a lot of VB coding behind the scenes. I would like to begin to distribute my programs for $$$. From what I have researched, distribution through Access is somewhat of a pain. So, now it looks like I have to make the jump and translate them into a VB front end, and have Access as the database on the back end.

I have never written a complete application in VB before, even though I tend to do a lot of coding in Access. I am looking for any advise, tips, etc, how to proceed with the translation to a full blown VB. Anything that would make this seemingly large task a bit smaller and easier.

Also, comments are appreciated about any comparisions between using Access as a front end, as opposed to using VB as the front end. If there is an existing FAQ or thread on this, please point me in that direction.

Thanks for your help.

 

[tbl]

This is a classic problem !
I take it that you have written lots of aplications in VBA within Access databases. Unfortunately there is very little demand for this commercially. What people want, as you say, are programs that are capable of performing various useful tasks using Access as the means of storing data. This approach leads you away from using VBA as no one is likely to want to use Excel to perform operations on an an Access database !
Once you have decided to use VB instead of VBA, then you might as well go straight to VB.Net or C#. This is the way I went for exactly those reasons. Writing VB.Net is very similar to writing VBA and .Net is a lot more powerful.

Hope this helps,

Richard

 

[ycim]

Well, you have definately confirmed that I am not alone in my quest! I wish Microsoft would have made this conversion a little easier. It is comforting to know that VB.net is similiar to VBA. To learn a new language is a very time consuming project and not one that I am looking forward to!

So...long story short...time to upgrade for me, I think! Thanks for your advice, and I am certain that I will see more of you in the vb.net forums!

Thanks

 

[tbl]

I think that Microsoft have made the change-over fairly easy. It is certainly not to be underestimated, but you have to understand that you are changing from a spoon-fed environment (VBA) where everything to do with the application you are working in is provided and documented for you within the VBA environment. If you have ever tried to program Reflection or Lotus Notes in VBA you would realise how frustrating the lack of documentation is when you leave the Office environment.
VB.Net does provide a much bigger environment and does include documentation for all .Net controls. It is not significantly more difficult than VB6, but infinitely more powerful. The extra work in learning VB.Net or C# is not that you have to switch from programming in VBA to doing it in VB.Net, but that you are working in a much more elaborate language which is simply more difficult to progress in. The first big problem is the cost !! The second is the size of the package !!

all the best,

Richard

 

[RoyVidar]

Expensive - I would say that depends on what you choose.

The Microsoft .NET SDK 1.1 can be downloaded for free.

There's at least one OpenSource alternative IDE for C# and VB.Net programming SharpDevelop.

Roy-Vidar