Upgrading Access database to VB6

[awhitsel]

I wrote an application using Access 2002/XP, and my supervisor wants to have it upgraded to Visual Basic 6 with a SQL Server 2000 back-end.

Is there a program or utility available that can automatically do this, or will I be stuck in re-writing the entire program from scratch.

Please advise.

Thanks.

 

[jsteph]

In my opinion, you should re-write the entire thing. You can certainly use your existing logic as a template, and in many cases the code can be ported with little change, but I would steer clear of any 'automatic' utility that promises to convert this.

In this were a very simple app, with few users, it may seem to make sense to export the Access tables to sql-server, then set up a data control link to these tables, and bind the datasource to a vb form. This is not recommended, but as I said, if you're looking for a quick & dirty way, the data control is it.

However, for anything semi-complex, or with many users, you really want to re-do the whole architecture. Live, bound data-controls/grids are really problematic from a record-locking standpoint, for instance. You really want to use unbound forms and grids, etc. and do all updates, inserts, etc. in SQL.

It's a lot of extra effort but it is highly recommended that you take that approach as opposed to the data-control, bound grid approach.
--Jim

 

[AlexCuse]

A second vote for re-write.

If you are not going to take advantage of the benefits you get by converting to SQL Server Backend, may as well just stay in access.

Just my two cents...

Alex

A wise man once said
"The only thing normal about database guys is their tables".

 

[jadams0173]

A third vote. I just moved 2 access 2k databases to sql server 2k. As mentioned above stay clear of bound data controls if at all possible and use stored procedures where you can instead of queries. It will take more time (probably) but you will be most certainly happier with the quality and speed it you do.

Also, I used the upsizing wizard in access to get my tables and data to sql server.

I tried to have patience but it took to long! -DW

 

[missinglinq]

I can understand the reasons for upgrading to a SQL Server 2000 back-end (although I'm always skeptical when a "supervisor" decides something technical needs to be done; all too often it's because they've read an article somewhere) but why not move to a SQL Server back-end and retain the Access front-end?

The Missinglinq

Richmond, Virginia

There's ALWAYS more than one way to skin a cat!

 

[AlexCuse]

Excellent point missinglinq! Especially about supervisors' reasons ;-)

And if you can't keep the Access front end, another thing to consider is that because you would in essence be starting from scratch, it might be a good idea to build it in vb.net. I love vb6, but .net seems to be the way everything is going these days. I have read that conversion from vb6 to .net can be extremely painful, so you may as well skip this step.



A wise man once said
"The only thing normal about database guys is their tables".