OpenReport Method and Access security [RESOLVED]

[oleg]

I have a report that is being printed from a vb application, my concern is will the following code work on the password protected database??? and if it won't is there a way to get around it?

Set AccessDB = New Access.Application
AccessDB.OpenCurrentDatabase strDB
AccessDB.DoCmd.OpenReport strReport, acViewPreview, strFilter, strWhere
AccessDB.Visible = True
Set AccessDB = Nothing

[RobDog888]

No, your current code will not open a password protected database. All it needs is a simple syntax
change to specify shared open mode and also to pass the password.

Set AccessDB = New Access.Application
AccessDB.OpenCurrentDatabase strDB, False, "YourPassword"
AccessDB.DoCmd.OpenReport strReport, acViewPreview, strFilter, strWhere
AccessDB.Visible = True
Set AccessDB = Nothing

[oleg]

doesn't seem to work for access 2000

[RobDog888]

Give me a minute and I will test on my other system w/2000.

[RobDog888]

Ok, heres the bad news. Access 200 does not support the password parameter. The "good" (I guess) news is
that it started support on Access XP.

The DoCmd command is only available when using the Access Application Object and not in DAO.

There are other methods to display a Report object like the SysCmd object.

[oleg]

how does the SysCmd command work and will it allow me to use a password parameter. Rob, I can't thank you enough for your help.

[RobDog888]

Seems that the SysCmd can only get the status of the object passed to it and not actually instanciate an
instance of a Report.

I'll look for another way to show a Report.

[oleg]

I'll look for another way to show a Report.

How about Access 2003? Does it have the capability to pass the pasword parameter to the OpenCurrentDatabase statement?

[RobDog888]

Access 2002 (XP) and 2003 do have that ability. Is that an option to upgrade?

[oleg]

no upgrade is necessary the client that i am writing for has Access 2003 as a standard application, I am writing the application with Access 2000 for a backend, thus it works itself out. RobDog you've been extremely helpful in this matter. Thanks a million.

[RobDog888]

Cool! Easy fix Always glad to help.

Edit: just noticed that you have been a member for a few years
Glad to see you back.

[oleg]

Yeah, I used to be a programmer, then I lost my job for a while, now i'm trying to get back to the market. hopefully everything will work out. Thanks again Rob.

[oleg]

a new problem arose on a horizon, . I thought that by adding the passowrd parameter to my code will set me home free, but when trying to comple the executable it gave me a compile error wrong nuber of arguments. is there a way to reference Access 11 object library without having access 2003? what is the procedure for that?

[RobDog888]

Yes, you need to do Late Binding instead of Early Binding. When you late bind vb doesnt check for the needed references when compiling. When you run your program you need to have 2003 installed.

When you late bind you dont get the intellisense since vb doesnt know what object you are referencing to.
Also remove the reference to Access after you modify the code as follows.

Dim AccessDB As Object
 
Set AccessDB = CreateObject("Access.Application")
AccessDB.OpenCurrentDatabase strDB, False, "YourPassword"
AccessDB.DoCmd.OpenReport strReport, acViewPreview, strFilter, strWhere
AccessDB.Visible = True
Set AccessDB = Nothing

[oleg]

Thanks Rob, once again you are the man!!!!

[RobDog888]

No prob. Glad to help.