Common Functions that you can use in Report Header or Footer Sections, while designing Reports, are given below. Copy and Paste the VB Code into a Global Module of your database and save it.

Write the Functions in the form of a Formula in Text Boxes as shown in the Syntax.

Function to display formatted Page Numbers.

Function : PageNo()

Syntax : =PageNo([page],[pages])

Result : Page : 1 / XXX where XXX stands for maximum number of pages of the Report.

Note : [page],[pages] are MS-Access built-in Report Variables and must be used as shown.


Public Function PageNo(ByVal pg As Variant, _ByVal pgs As Variant) As String
'Output   : Page: 1/25
'         : Call from a Report Text Box control
'Author   : a.p.r. pillai
'Date     : 01/09/2007
'Remarks  : The Formatted Text takes up 15 character space
Dim strPg As String, k As Integer

On Error GoTo PageNo_Err

pg = Nz(pg, 0): pgs = Nz(pgs, 0)
strPg = Format(pg) & "/" & Format(pgs)
k = Len(strPg)

If k < 15 Then
   strPg = String(15 - k, "*") & strPg
End If

strPg = "Page: " & strPg

For k = 1 To Len(strPg)
  If Mid(strPg, k, 1) = "*" Then
    Mid(strPg, k, 1) = Chr(32)

PageNo = strPg

Exit Function

Msgbox Err.Description,, "PageNo()"
PageNo = "Page : "
Resume PageNo_Exit
End Function

Function to print Period with formatted Start-Date and End-Date on Report Header or Footer.

Function : Period()

Syntax : =Period([StartDate], [EndDate])

Result : Period: 15/09/2007 To 30/09/2007

Note: Format String in the Code may be modified for country specific date format.


Public Function Period(ByVal prdFrm As Date, _ByVal PrdTo As Date) As String
'Output   : Period: dd/mm/yyyy To dd/mm/yyyy
'         : Call from Report control to insert date
'Author   : a.p.r. pillai
'Date     : 01/09/2007
'Remarks  : Modify Format String for Country specific date format.

On Error GoTo Period_Err

Period = "Period: " & Format(prdFrm, "dd/mm/yyyy") & " To " & Format(PrdTo, "dd/mm/yyyy")

Exit Function

MsgBox Err.Description,, "Period()"Resume Period_Exit
End Function

Function to print formatted System Date in Header or Footer of the Report.


Function : Dated()


Syntax: Dated()


Result : Dated: 15/09/2007



Public Function Dated() As String
'Output  : Dated: 20/08/2007
'        : Call from Report Text Box control
'Author  : a.p.r. pillai    Date    : 01/09/2007
'Remarks  : Change Format String for Country specific Date Format
On Error GoTo Dated_Err

Dated = "Date: " & Format(Date, "dd/mm/yyyy")

Exit Function

MsgBox Err.Description,, "Dated()"
Resume Dated_Exit
End Function 

You can design the full Page Footer of a Report with Date and Page Number at one go with a single Function. Read my earlier Article: Reports . . . Page Border. Use the Function DrawPageFooter() Code & procedure explained there.

You can add frequently used Expressions or Routines as Public Functions into a Global Module of your Database and Run from where you need them (Forms, Reports, Query Expressions etc.) rather than repeating the code everywhere.

You can further enhance the use of all the common Functions that you have, by organizing them into a separate Database and link this as a Library File into your New Projects. In this case, if you have any common Form (like MS-Access Form Wizard) that you have designed then that also can be placed in the Library Database. When you call the Library Function from your Project, which uses the common Form, MS-Access first checks for the Form in the Library Database, if not found there then opens it from your current Project.

Follow the procedure explained in the earlier Post Command Button Animation for linking the Essential Library Files to your Project. Your Library Database’s name may not appear in the installed library file’s list. Browse to the location of the database, attach it to the library list and select it.

You can save this Library file into a compiled state by converting it into a .MDE File. Select Tools – – > Database Utilities – – > Make MDE File to convert and save the current database into .MDE Format. You cannot edit the code in the .MDE database. Preserve the .MDB file for future changes and compilation, if it becomes necessary.

When you install your Project don’t forget to install your common Library Database also along with it and attach it to your Project in the new location. That rule goes for other built-in Library Files also in the new location. It is likely that the built-in Library File Versions are different on the new machine, from what you have used at design time. This can happen if other Visual Basic based Applications are already installed earlier in the target machine. Such items will show as MISSING in the selected Library Files’ List and you must attach the available Version of the file on the installed location.

If your Project is shared by different Versions of MS-Office Applications, then it is a good idea to attach an older version of the built-in library file (if available) to the project.

Refer the earlier Post on Sharing an Older Version Database under the topic: Ms-Access Security.