• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 253
  • Last Modified:

Access reports in VB

Is it possible to 'use' access reports through VB?

can you open access and get the report open in print preview mode, or is there some way to do it without opening access? (i.e. a seperate report viewer/printer program hidden somewhere)

simple! but i still cant seem to do it :|

1 Solution
Éric MoreauSenior .Net ConsultantCommented:
it is not possible because the reports need to be runned by the Access engine. The only way is to rebuild your reports using a real reporting engine (Crystal Report, Active Report, ...)
I have just been having the same issue.  emoreau is right that you need the Access engine which means Access will have to be installed on any PC running the VB app that launches the report (which is a real pain for me).

Here is the code I am using until I can find something better.

                Set lAccess = CreateObject("Access.Application")
                Set db = lAccess.Application.DBEngine.Workspaces(0).OpenDatabase(IPDBNAME, 0, False, ";pwd=X1JFH9")
                lAccess.Visible = False
                lAccess.OpenCurrentDatabase IPDBNAME, False
                Set db = Nothing
                lintResult = SetForegroundWindow(lAccess.hWndAccessApp)
                'The report should open in printpreview
                If RptDest = 0 Then
                    lAccess.DoCmd.OpenReport UCase(LstRptFile(lstReports.ListIndex)), acViewPreview
                    lintResult = ShowWindow(lAccess.hWndAccessApp, SW_SHOWNORMAL)
                'The report should just print
                    lAccess.DoCmd.OpenReport UCase(LstRptFile(lstReports.ListIndex)), acViewNormal
                    lintResult = CloseHandle(lAccess.hWndAccessApp)
                    Set lAccess = Nothing
                End If

I am using some api calls in this code to ensure that the report window is active once it is opened.

You can also check out my question:

For me security of the database was an issue so I had to add some additional security in Access itself as well.
you can open access and have a report open in print preview mode with an access autorun macro, then call the report with printpreview

but this will work only with ONE report you choose

maybe if you try diferent access mdb with one report in each (yiack!!!)

Never miss a deadline with monday.com

The revolutionary project management tool is here!   Plan visually with a single glance and make sure your projects get done.

SiM99Author Commented:

aight, im trying your code out. (Didnt know you could access docmd, cool :)
but, err... what does the RptDest variable hold, and what vartype is it?
SiM99Author Commented:
i'm assuming that lAccess was a Access.Application...
and what variable type was db?
SiM99Author Commented:
One more thing, how have you you made your user accounts?

Tried the security/user accounts menu option, but that makes them in the current system workspace, so they wouldn't be transferred with the database.

Have you used this method, or have you attatched the accounts to your database?
Sorry for not commenting better.

RptDest is just an integer.  It is just a variable I set elsewhere to tell if the report should just print or if it should open in print preview.  If you are trying to open it in print preview you can get rid of that entire if statement and just use what is in the Else part.

Correct lAccess is Access.Application
and db is Object

As far as the security your right.  I had just done this yesterday myself and had only tested it locally.  I'm pretty new to Access security as in the past I have only used Access as a back-end database where I would set the database password and not worry about individual user rights.  I guess I'll have to look into this some more.
OK about the security.  If you do a search in Access help about security and Access workgroups you can read about all of this better than I will explain here, but here is what I'm planning to do.

When you define permissions with user accounts it creates a workgroup information file (usually where Access is installed) and Access uses that file for security locally.  However, using a utility called the WorkGroup Administrator you can put the file on in the network location as your database and then using WorkGroup Administrator on the client machines tell them to get their security information from the workgroup information file on the network, not thier own local copy.

I still don't like this a whole lot, but I'm going to try it initially and see how it works.
SiM99Author Commented:
I had also found the information about the workspaces, but it seems silly to try and get a client to install a workspace - in our situation anyway, we dont have all clients networked! :)

Got the reports to open at least...
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now