Converting an Access application to a Visual Basic Program

[Jman]

I am trying to convert several Access applications that I have written in Access using VBA to executeable VB programs I seem to be running into some problems executing the docmd. in Visual Basic if I understand correctly the Docmd is not valid in Visual Basic 6.0 Well how can I if I can import text to a table using visual Basic 6.0 and How can I have The Visual Basic6.0 forms and controls recognize my Access tables and queries Can I use the ADO controls in Visual Basic6.0 and if I can do I need to use a different control for each table and query then when I compile the application will I need to compile and package the application with The database that the ado controls point to? Questions like this are really giving me a hard time I really thought that this conversion was simply a matter of cut and paste from access to Visual Basic Any help is greatly apperciated I cam be reached at my email address which is John.Corrigan@stewart.army.mil
Thanks in advance
John

 

[ElsVanMiert]

My personal experience is that converted applications in VB never have 100% of the functionality of the original ACCESS applications.
So the real question is: WHY are you no longer satisfied with ACCESS?

 

[Pat Hartman]

The clue to your problem can be found in this line I quote from the docmd help entries:
"You can use the methods of the DoCmd object to run Microsoft Access actions from Visual Basic."

The DoCmd object runs Microsoft "Access" actions from VB code. Native VB will have equivalents for most of these actions. You'll need to find out what they are.

 

[Jman]

I am satisfied with the Access applications but I am a contract Access developer and a new one at that and in a meeting with the client I was explaining how to maintain the databases that I created and he explained that he wanted these to be maintance free???
Well without thinking I told him that the only way to have a database that required no maintaince would be to have a executable program as oppossed to a database well that was a mistake the next day he bought VB 6.0 and here I am. Like I said I am really new to this.

 

[Talismanic]

Jman I am faced with the same thing but for different reasons.

Here is a tutorial I found that will walk you through using an Access database with Visual Basic. Hope it helps!

Visual Basic Database Tutorial - Part 1

Without knowing much about it yet, it seems like you get the best of both worlds when combining the two. If you need help with VB let me know and I will round up some links for VB boards similar to this one.

 

[Jman]

I think I could use those VB links I took a look at the tutorial link and I think it would help me but it was a weekly thing and the stuff I need to know like today The tutorial goes over in almost a month from now??? go figure thanks for all your help.

 

[Atomic Shrimp]

erm,

although the tutorial is weekly, you can get to all of the instalments from the page at the end:
http://www.vbworld.com/databases/dbtutorial/index5.html

Mike

 

[Talismanic]

Ok here is the list that I have.

SearchVB

VB Help

VB Explorer

VB Explorer seems to be the most active of the three I listed.

 

[bodvoc]

To VB or Not VB

Hi all

I need to do this as well.. speed over network and acident prone Users force making an exe.

I have been told that there is a third party tool for converting an Access db in to Delphi / VB / and - or other db, but can't find it on the net.

Does anyone know of this?? is there a quick fix for the .docmd??

Thanks for your help..

 

[andrewf10]

My fairly limited knowledge of VB6 suggests that there's no easy fix other than to go through each of the lines of code as Pat suggested.

For example:

Docmd.Quit (in VBA) = End (in VB6)

 

[bodvoc]

Thanks for that, oh well... I wonder if there is any third party VB clone that imports as is.....

back to the code ;( Thanks again....

 

[Pat Hartman]

I think that if you are looking for performance improvements, you will find that migrating your data from Access to SQL server or some other "real" RDBMS will provide more of an improvement than leaving the data in Access tables and converting the FE to VB.

If you are not already a "real" programmer, you'll need to get up to speed. There is a lot of code behind VB forms and the report writer is no where near as good as Access.

 

[bodvoc]

More of a hobbiest programmer though did train and work as C++ and Pacsal Programmer. . Looks like it will have to be SQL for them.. Perhaps they can get someone to donate an older version of SQL or get a Gov. Grant for the update.... Thanks for you help...