How to convert Access database into installable application s/w in VB 1

[Raza]

Hi <br>
i just want how to convert my database form access97 to installable vb program. i dont know much to program in vb and want to know abou some easy tips to do this job. i will prefer to program in vb5. tell me if i can convert all my reports, qureies, tables, relations etc form access to vb.<br>
thanks.<br>
raza

 

[johnfra]

Raza,<br>
you purchased the wrong application, you need the Access Developers kit not VB. If you want a database in VB you pretty well have to create it in VB. You can manipulate an existing Access database with VB but I assume that you want a database that you can distribute with out paying lisence fees, in the case youu need the Access SDK.<br>
Regards,<br>
John

 

[elizabeth]

BTW, the kit is called different names in different Access versions and different documents. It can be referred to as SDK (Software Developer's Kit), ODE (Office Dev Edition), etc.

 

[Ari]

I have a similar issue in that I am having trouble getting VB 6.0 to recognize queries in Access 2000. All we're trying to do is make some VB frontends for Access databases to save resources and process time with all the Access overhead.<br>
<br>
The Microsoft site wasn't very helpful and the new ADO controls were even less helpful...What can you recommend?

 

[elizabeth]

I don't get why you would put a VB front end on Access. My understanding of the product's strength and intended use was (1) a front end or (2) a small application with few users. What am I missing?

 

[Raza]

Ok I need to put front end for Access in VB. I may be developing the application for 3-4 users on winnt 4.0 with some security level protection.

 

[bitbrain]

Elizabeth,<br>
<br>
As you know, Access is a full-featured application development tool that supports forms, reports, VBA, etc. The underlying database engine is called JET (MSJET35.DLL).<br>
<br>
JET also ships with VB. If I'm not mistaken, you can distribute the JET dll without license fees.<br>
<br>
There are many reasons why you would want to build a VB app. that has a JET back-end. One reason would be that vb .EXE's are much tighter (smaller) than all of the bloat that goes along with Access - making them easier to distribute and not forcing users to purchase & install Access.<br>
<br>

 

[dajo]

I have a similar issue. Do I have to have MS Access installed on a destination machine where I will install a VB project that creates a MDB database and uses it from then on, or does the executable contain all the files necessary for its creation and subsequent manipulation?

 

[dalec]

Ditto! I've had nothing but hell installing my VB ap. I use an access 2000 database, and even installing dcom95/98 (whichever is needed) and then installing mdac and jet (latest versions) I still get a runtime error when trying to open the database. This doesnt happen all the time, sometimes installing these files will work on a target machine, but more often than not, I have to install access on the machine then uninstall it for the application to work correctly. Any better clues?

TIA,
Dale

 

[Foada]

dalec,

You should only need the mdac and jet to connect to your Access database. Both are very picky about the versions, ie the version you develop with needs to be the version you distribute with your app. The other thing that may give you a problem is the connection string to the database. If you are using the ADODC control it has a tendency to hold the path you used during development and not the database path on the deployed app.

 

[1127]

If You only want to install the Access application and to start it with an exe then You have to create a VB application with a form.
Add to this form every ActiveX controls that u use in the Access application.
In form Load event You start the Access aplication and unload the form.
Create an install kitt and add every file that You need to run the Access app (mdb, mde, jpg etc.)
Create the runtime install kitt off Access.
After You install the application instal the runtime too.
You can even modify the VB install kitt to install the Runtime automatically.
MAKE A BACKUP OF Setup1.exe!
If You use the Access Calendar control DON'T include it in the install kitt! (only if You have the SP5 for VB)

 

[dalec]

Thanks for the reply, I know for sure that the error is encountered when I set the workarea:

   DBName = App.Path & "\FundData.mdb"
   Set Wk_area = CreateWorkspace("ODBCWorkspace", "admin", "", dbUseODBC)
   Workspaces.Append Wk_area
   Set DBSFund = OpenDatabase(DBName, False, False)

I havent ran the microsoft mdac version checker on the systems prior to installation, do you think I need to start registering the data Dll's manually. One thing I just checked and I am using the DAO 3.6 object library. I was hopeing moving to the Wise installer would have fixed this problem, any further help is appreciated.

Thanks,
Dale