DAO and MS Access

[oyad]

am using DAO in my VB project with means my Access has to be in MS Access 97. its working fine but i want to passwordthe mdb file. i dont know how to open the file in VB, icant set the password property or whats wrong
dayo

[BruceG]

Set objDB = OpenDatabase("C:\SomePath\SomeName.mdb", _
                              True, False, ";pwd=yourpassword")

[RobDog888]

You need to set the password in Access first. Then you need to create a DAO workspace to connect and pass a password.

Private wsDB As Workspace
Private dbDB As Database
Set wsDB = DBEngine.CreateWorkspace("Username", "admin", "pwd")
Set dbDB = wsDB.OpenDatabase("DBName")

[haruki]

Weird, Im using Access 2003 with DAO. I dont think its limited to the old 97 version.

[BruceG]

Correct, DAO still lives on.

[oyad]

Weird, Im using Access 2003 with DAO. I dont think its limited to the old 97 version.

whenever i set the database name in the property window, when i get to the recordsource property,i receive an error, so i tried converting the mdb to 97, using tools menu in access and henceforth it worked fine. so i guessed it was the version. or what do u think?

[RobDog888]

I thought that in order to make changes to a 97 db you needed to convert it to 2000. Then it doesnt matter
which version of Access your running.

Are you using the Data control to try to connect?

[Hack]

I thought that in order to make changes to a 97 db you needed to convert it to 2000. Then it doesnt matter
which version of Access your running.

Are you using the Data control to try to connect?

If you have the lastest version of MDAC installed (2.7 I believe), you can use DAO with Access 2000 (I know...I accidentally converted my 97 Access copy of Biblio to Access 2000 against which I was running some DAO code on other problem on the forum, and got myself all bollaxed up because my version of MDAC wasn't up to date.)

[RobDog888]

Actually the latest MDAC is 2.8. Its included in Windows XP SP2, so if the thread starter is running that then
that could be an issue?

[GregLoutsenko]

implementing just a single password potentially is a bad idea. if in the future u r trying to expand the app for multi users u will not be able to create users, so u cant set access permision. look up workgroup info files for further info on this.

ps
i am coding a security sys for my app at the minute which uses workgroup file and its prooving to be very hard as i cant find any good tutorials on it and the documentation isnt very good

[oyad]

plz, when i try to open the app on an OS with no VB installed , i received errors,
something like this

runtime error "713"
class not registered,looking for object with CLSID: {00000010-0000-0010-8000-00AA00602EA4}

how am i goona fix this thru my VB code (including other means)?
waiting

[si_the_geek]

You can't fix it in code, you need to create an installation package for your program.

You can use the Package & Deployment Wizard that comes with VB (it should be on your start menu), or one of the many alternatives (see our Application Deployment forum for details & advice).

[oyad]

You can't fix it in code, you need to create an installation package for your program.

You can use the Package & Deployment Wizard that comes with VB (it should be on your start menu), or one of the many alternatives (see our Application Deployment forum for details & advice).

something like using regserver from VB from the application is launched and un-register it when the application closes because the application will not be distributed as an installation but as a stand -alone EXE on a CDROM disk

[Hack]

something like using regserver from VB from the application is launched and un-register it when the application closes because the application will not be distributed as an installation but as a stand -alone EXE on a CDROM disk

This isn't going to work as you are finding out. You must create an installation package that will include all of the dependancy files required by your .Exe or the program will never, ever, run.

The installation package, not the .Exe should be on the CD, and the customer should be provided with instructions on how to run the install.

[oyad]

This isn't going to work as you are finding out. You must create an installation package that will include all of the dependancy files required by your .Exe or the program will never, ever, run.

The installation package, not the .Exe should be on the CD, and the customer should be provided with instructions on how to run the install.

hi, plz can u help, i just discovered that the rest app had similar problems-like error-one of its dependences not file or missing file , for tabctl32.ocx,winsock.ocx,flxgrd.ocx etc. any tip or solution.
plz, am waiting!
oyad

[RobDog888]

Like Hack suggested, you need to create an installation package. You can use the P&D Wizard that
comes with VB to create one or download one from the Application Deployment FAQ forum.