Switching from Access to VB

[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. (I also posted this in another forum in error...sorry if you are reading a duplication).

 

[RoyVidar]

I'm only an Access guy myself, but I think moving to VB6 can become quite a step, of course depending on the complexity of the existing apps, due to rather different object models (have a look at MichaelRed's reply here thread709-1050793, if you're thinking of "converting" existing apps).

Why not take it even a step further, switching to VB.Net, since VB6 is discontinued?

It will be a bit harder to learn, but I believe it will perhaps give better payoff in the future.

Roy-Vidar

 

[tony00]

As you learn VBasic, please don't use the DataControl. IT is very slow and inefficient.

Try to get a hang of ADO. It's not too complicated (a little effort is reqired).

 

[Golom]

Depends at least to some extent on how "religious" you've been about separating presentation logic from business logic in your Access code. If most of the business logic is in your forms then it's going to be difficult to migrate due to the different object model that RoyVidar mentioned.

If you have kept business logic at the module or class level then it should migrate ... not exactly painlessly ... but more simply than redesigning the whole application in VB.

Access and VB, despite the commonality of the coding language, are really two different programming environments and attempting a literal translation of one into the other will probably turn a good Access application into a mediocre VB application. Be prepared to critically examine what you have done in Access in light of capabilities that exist or don't exist in VB. The really difficult thing to do is to abandon an approach that worked well in one environment in favor of a completely different and untried one in another.

 

[ycim]

I hadn't realized that there was so much difference. I am not sure that I was prepared for that. Definately up to the challenge, but I just didn't expect it. I think that I had better take the concepts I programmed in Access, and start over again in VB.

I am glad someone mentioned the data control in VB. I have dabbled a bit, and it is what I am using. I will have to explore ADO. Any suggestions what to look at first? Is there a good FAQ or thread you have seen?

Thanks for all your help and advise. I definately appreciate it.