Access to VB conversion

[groengoen]

Considering the difficulties in packaging Access software, I am wondering about the feasibility of converting my Access project to VB and distributing that instead. Has anyone done this and if so how difficult would it be. Does it mean a complete rewrite or can I use existing forms, reports and coding etc.

 

[boblarson]

It would be extremely difficult for you as you cannot use any of the access objects, other than tables and queries.

 

[Moniker]

Recreating the forms to match what you have in Access would be the first struggle. The reports are a whole other beast. The code, while somewhat similar, would have to change pretty drastically.

It's not impossible, but it's not a "click here to convert to VB" type of action either. If the DB is still pretty small, it's not that hard, but if it's a robust project, you better off doing as Bob said; I.e., maintaining your current Tables and Queries and then starting from scratch on the other stuff.

 

[boblarson]

...maintaining your current Tables and Queries and then starting from scratch on the other stuff.

There is no choice in building forms and reports. You cannot utilize forms and reports outside of the database, so manually rebuilding the forms and reports is GOING to happen if this is undertaken. There may be some tools out there that will convert them for you, but those most assuredly will cost money.

Also, when you move to doing it as a VB program, you lose a lot of Access's internal handling of things and you will soon find out how much Access actually does for you.

So, while it isn't impossible to do, it will be a LOT of work so you need to make sure that the benefits will outweigh the costs.

 

[groengoen]

Thanks guys. That is just what I needed to know. It will probably be better to persevere with the packaging wizard for another while.

Geoff.

 

[RodgerDJr]

I just wanted to see if anyone knew of anything out there now that would help in this process? I have a database that I have been developing for many years and really would like to take the next step and move to SQL and VB. I know this will take a long time, but I figured the database has been pretty stable with very few changes, so this would be a good time. what a wonderful way to learn something new.

 

[Banana]

IMHO, while it may be worthwhile to move to SQl as a backend, it is much more of a stretch to want to move away from Access as front-end primarily because it is faster and easier to develop in Access. If you needed to added a new column, it's just a textbox, a query and binding that needs to be changed in Access. In any other development environment, you have to take more steps to do the same.

 

[RodgerDJr]

That is what I thought. I have been doing a lot of development with SQL 2005 for my real job. I think I might just take a small database that I has 5 forms and just a few tables and see how agenizing it is.

 

[DCrake]

Simple Software Solutions

To interject, I am a member of a another form that is orientated to VB www.planetsourcecode.com.

As I also do a majority of my work in VB and find that legacy programs in Access need to upgraded to VB I found a submission on how to convert an Access program to VB. I will see if I can dig it out. I tried it once but can't remember how sucessful it was.

 

[DCrake]

Simple Software Solutions

Here is a link to a website that has the software to do thishttp://www.tvobjects.com/products/Convert-Access-to-VB.html

and this one to

http://www.filetransit.com/download.php?id=4399

 

[DCrake]

Simple Software Solutions

Hi Pat,

What do you mean when you say VB is at a dead end?

 

[Banana]

If I'm not mistaken the classic VB passed its end of life date; Microsoft will not be supporting this anymore. Not that those VB6 applications already running will suddenly go belly up, but as Microsoft develop .NET framework, it's going to get harder and harder to do stuff in VB6.