access 2007 vba bible phần 4 potx

Apply the Calibri 9 pt font to the entire worksheet: .Range(“A:F”).Font.Name = “Calibri” .Range(“A:F”).Font.Size = 9 Apply hairline borders to the entire worksheet: .Range(“A:F”).Borders(xlDiagonalDown).LineStyle = _ xlNone .Range(“A:F”).Borders(xlDiagonalUp).LineStyle = xlNone .Range(“A:F”).Borders(xlEdgeLeft).LineStyle = _ xlContinuous .Range(“A:F”).Borders(xlEdgeLeft).Weight = xlHairline .Range(“A:F”).Borders(xlEdgeLeft).ColorIndex = _ xlAutomatic .Range(“A:F”).Borders(xlEdgeTop).LineStyle = _ xlContinuous .Range(“A:F”).Borders(xlEdgeTop).Weight = xlHairline .Range(“A:F”).Borders(xlEdgeTop).ColorIndex = _ xlAutomatic .Range(“A:F”).Borders(xlEdgeBottom).LineStyle = _ xlContinuous .Range(“A:F”).Borders(xlEdgeBottom).Weight = _ xlHairline .Range(“A:F”).Borders(xlEdgeBottom).ColorIndex = _ xlAutomatic .Range(“A:F”).Borders(xlEdgeRight).LineStyle = _ xlContinuous .Range(“A:F”).Borders(xlEdgeRight).Weight = _ xlHairline .Range(“A:F”).Borders(xlEdgeRight).ColorIndex = _ xlAutomatic .Range(“A:F”).Borders(xlInsideVertical).LineStyle = _ xlContinuous .Range(“A:F”).Borders(xlInsideVertical).Weight = _ xlHairline .Range(“A:F”).Borders(xlInsideVertical).ColorIndex = _ xlAutomatic .Range(“A:F”).Borders(xlInsideHorizontal).LineStyle = _ xlContinuous .Range(“A:F”).Borders(xlInsideHorizontal).Weight = _ xlHairline .Range(“A:F”).Borders(xlInsideHorizontal).LineStyle = _ xlContinuous Set the widths of the columns: .Range(“A:A”).ColumnWidth = 25 .Range(“B:B”).ColumnWidth = 15 .Range(“C:C”).ColumnWidth = 15 197 Working with Excel Worksheets 7 12_047026 ch07.qxp 4/2/07 9:44 PM Page 197 .Range(“D:D”).ColumnWidth = 20 .Range(“E:E”).ColumnWidth = 15 .Range(“F:F”).ColumnWidth = 20 Insert blank rows at top of worksheet: .Range(“1:1”).Insert Shift:=xlDown .Range(“1:1”).Insert Shift:=xlDown .Range(“1:1”).Insert Shift:=xlDown .Range(“1:1”).Insert Shift:=xlDown Format the column headings row: With .Range(“5:5”) .Font.Size = 10 .Font.Bold = True .Borders(xlEdgeTop).Weight = xlMedium .Borders(xlEdgeBottom).Weight = xlMedium .Interior.ColorIndex = 15 .Interior.Pattern = xlSolid .Interior.PatternColorIndex = xlAutomatic .RowHeight = 15 .VerticalAlignment = xlBottom .HorizontalAlignment = xlCenter .WrapText = True End With Insert and format title text: .Range(“A1:F1”).HorizontalAlignment = xlCenter .Range(“A1:F1”).VerticalAlignment = xlBottom .Range(“A1:F1”).WrapText = False .Range(“A1:F1”).Orientation = 0 .Range(“A1:F1”).ShrinkToFit = False .Range(“A1:F1”).MergeCells = True .Range(“A1:F1”).Borders(xlDiagonalDown).LineStyle = _ xlNone .Range(“A1:F1”).Borders(xlDiagonalUp).LineStyle = _ xlNone .Range(“A1:F1”).Borders(xlEdgeLeft).LineStyle = xlNone .Range(“A1:F1”).Borders(xlEdgeTop).LineStyle = xlNone .Range(“A1:F1”).Borders(xlEdgeBottom).LineStyle = _ xlNone .Range(“A1:F1”).Borders(xlEdgeRight).LineStyle = _ xlNone .Range(“A1:F1”).Borders(xlInsideVertical).LineStyle = _ xlNone .Range(“A2:F2”).HorizontalAlignment = xlCenter 198 Writing VBA Code to Exchange Data between Office Components Part II 12_047026 ch07.qxp 4/2/07 9:44 PM Page 198 .Range(“A2:F2”).VerticalAlignment = xlBottom .Range(“A2:F2”).WrapText = False .Range(“A2:F2”).Orientation = 0 .Range(“A2:F2”).ShrinkToFit = False .Range(“A2:F2”).MergeCells = True .Range(“A2:F2”).Borders(xlDiagonalDown).LineStyle = _ xlNone .Range(“A2:F2”).Borders(xlDiagonalUp).LineStyle = _ xlNone .Range(“A2:F2”).Borders(xlEdgeLeft).LineStyle = xlNone .Range(“A2:F2”).Borders(xlEdgeTop).LineStyle = xlNone .Range(“A2:F2”).Borders(xlEdgeBottom).LineStyle = _ xlNone .Range(“A2:F2”).Borders(xlEdgeRight).LineStyle = xlNone .Range(“A2:F2”).Borders(xlInsideVertical).LineStyle = _ xlNone .Range(“A3:F3”).HorizontalAlignment = xlCenter .Range(“A3:F3”).VerticalAlignment = xlBottom .Range(“A3:F3”).WrapText = False .Range(“A3:F3”).Orientation = 0 .Range(“A3:F3”).ShrinkToFit = False .Range(“A3:F3”).MergeCells = True .Range(“A3:F3”).Borders(xlDiagonalDown).LineStyle = _ xlNone .Range(“A3:F3”).Borders(xlDiagonalUp).LineStyle = _ xlNone .Range(“A3:F3”).Borders(xlEdgeLeft).LineStyle = xlNone .Range(“A3:F3”).Borders(xlEdgeTop).LineStyle = xlNone .Range(“A3:F3”).Borders(xlEdgeBottom).LineStyle = _ xlNone .Range(“A3:F3”).Borders(xlEdgeRight).LineStyle = xlNone .Range(“A3:F3”).Borders(xlInsideVertical).LineStyle = _ xlNone .Range(“A4:F4”).MergeCells = True .Range(“A4:F4”).Borders(xlDiagonalDown).LineStyle = _ xlNone .Range(“A4:F4”).Borders(xlDiagonalUp).LineStyle = _ xlNone .Range(“A4:F4”).Borders(xlEdgeLeft).LineStyle = xlNone .Range(“A4:F4”).Borders(xlEdgeTop).LineStyle = xlNone .Range(“A4:F4”).Borders(xlEdgeRight).LineStyle = xlNone .Range(“A4:F4”).Borders(xlInsideVertical).LineStyle = _ xlNone .Range(“A1:A4”).Font.Size = 14 .Range(“A1:A4”).Font.Bold = True .Range(“A3”).Value = “As of “ & Date .Range(“A2”).Value = “Account Services” .Range(“A1”).Value = “Nation-wide Summary of” 199 Working with Excel Worksheets 7 12_047026 ch07.qxp 4/2/07 9:44 PM Page 199 Adjust worksheet print setup and margins: .PageSetup.PrintTitleRows = “$5:$5” .PageSetup.LeftFooter = “&F” .PageSetup.CenterFooter = “” .PageSetup.CenterHeader = “” .PageSetup.RightFooter = “Page &P” .PageSetup.Orientation = xlLandscape .PageSetup.PrintGridlines = False .PageSetup.Zoom = 90 End With Make worksheet visible and save it: appExcel.Application.Visible = True strPrompt = _ “Enter file name and path for saving worksheet” strTitle = “File name” strDefault = strSaveName strSaveName = InputBox(prompt:=strPrompt, _ Title:=strTitle, Default:=strDefault) wkb.SaveAs FileName:=strSaveName, _ FileFormat:=xlWorkbookDefault appExcel.Visible = True ErrorHandlerExit: Exit Function ErrorHandler: If Err = 429 Then Excel is not running; open Excel with CreateObject: Set appExcel = CreateObject(“Excel.Application”) Resume Next Else MsgBox “Error No: “ & Err.Number _ & “; Description: “ & Err.Description Resume ErrorHandlerExit End If End Function 200 Writing VBA Code to Exchange Data between Office Components Part II 12_047026 ch07.qxp 4/2/07 9:44 PM Page 200 Because the workbook was created in an older format, you will see “(Compatibility Mode)” in its title bar. The procedure starts by running a make-table query to create a table for export to Excel, then cre- ates a save name for the worksheet, and deletes the old worksheet file, if it exists. The data in the table created by the make-table query is then exported to a new Excel worksheet, using the TransferSpreadsheet method. The new worksheet is opened and activated, and various ranges in the worksheet are formatted, applying the Calibri font, hairline borders, and appropriate column widths for each column. I like to give tables created by make-table queries the prefix tmak, with the same base name as the query. This lets me know that a table was created by a make-table query, so I know that if I want to change it, I need to modify the query, not the table. Next, the procedure inserts blank rows at the top of the worksheet, and title text is inserted at the top; these header lines are then formatted with a gray background and upper and lower lines. Several print setup and margin settings are done next, and finally the worksheet is saved, with an InputBox so you can modify the save name, if desired. The finished worksheet is shown in Figure 7.8. FIGURE 7.8 An Excel worksheet formatted in VBA code. TIP TIP NOTE NOTE 201 Working with Excel Worksheets 7 12_047026 ch07.qxp 4/2/07 9:44 PM Page 201 As a quick way to find out the syntax for various Excel commands, open an Excel work- sheet, turn on the macro recorder, perform the actions, and then save the macro. Open the saved macro and copy the code to your Access procedure; with a little trimming of redundant arguments and editing to insert your variable names, it should work fine. Timesheets Almost any type of business (other than a one-person operation) needs a form for recording employees’ work hours and a way to print or electronically distribute the timesheet data. Often a company has used a paper form to record work hours for many years, and the electronic form needs to replicate the paper form. In some cases, there are specific government or industry stan- dard formats that must be used, or the data must be produced in a format that can be imported by a mainframe computer. You can use a preformatted Excel worksheet template to produce timesheets in the exact format you need and fill them with data from Access. One example of using timesheets in such a fashion is an engineering firm whose employees work on various projects for the company’s clients. Because the employees’ work hours (except for those assigned to internal projects) will be billed back to the clients, in this case a separate worksheet is needed for each employee’s work on a specific project per week, so a single employee might have several timesheets in a week. In the case of (for example) a scientific research establishment, where hours are not billed out to clients, one timesheet per employee, listing multiple projects in a week, would be more appropriate. The form frmWeeklyTimesheet (shown in Figure 7.9) is an Access front end for entering timesheet data that will be exported to Excel timesheets. This form lets you select an employee, client, and project, and fill in a timesheet for that employee. The assumption is that a separate timesheet is done for each client/project combination, so an employee can have multiple timesheets for a given week. The cboEmployeeID combo box’s row source is a union query that combines data from two queries: qryThisWeeksTimesheets, which lists the timesheets that have been filled in so far this week, and qryNeedTimesheets, which lists the employees who have not yet filled out a timesheet for this week. The resulting list displays all the employees, showing the timesheets that have been filled out so far, as illustrated in Figure 7.10. TIP TIP 202 Writing VBA Code to Exchange Data between Office Components Part II 12_047026 ch07.qxp 4/2/07 9:44 PM Page 202 FIGURE 7.9 An Access form for entering timesheet data for export to Excel. FIGURE 7.10 A combo box list showing timesheets for employees. After selecting an employee, the CurrentWeekEnding procedure calculates the week ending date (today, if it is Sunday, otherwise last Sunday) and fills the captions of the seven date labels on the form with the correct day of the week; the Manager name is also displayed in the Manager field (the light blue back color indicates that the text box is locked). (See Figure 7.11.) I give locked controls a light blue background (as opposed to a white background for editable controls) to give users a visual cue that they can’t enter or edit text in these controls. NOTE NOTE 203 Working with Excel Worksheets 7 12_047026 ch07.qxp 4/2/07 9:44 PM Page 203 FIGURE 7.11 Date information automatically filled in after selecting an employee. The CurrentWeekEnding and FillDateControls procedures are listed as follows: Public Function CurrentWeekEnding() As Date On Error GoTo ErrorHandler Dim dteToday As Date dteToday = Date Do While Weekday(dteToday) <> vbSunday dteToday = dteToday - 1 Debug.Print “Testing “ & dteToday Loop CurrentWeekEnding = dteToday ErrorHandlerExit: Exit Function ErrorHandler: MsgBox “Error No: “ & Err.Number & “; Description: “ & Err.Description Resume ErrorHandlerExit End Function 204 Writing VBA Code to Exchange Data between Office Components Part II 12_047026 ch07.qxp 4/2/07 9:44 PM Page 204 Private Sub FillDateControls() On Error GoTo ErrorHandler Dim strFormattedDate As String Fill week ending and weekday controls with text: Me![txtWeekEnding].Value = CurrentWeekEnding strFormattedDate = Format(DateAdd(“d”, -6, _ CDate(Me![WeekEnding])), “dddd, mmmm d, yyyy”) Me![lblMondayDate].Caption = strFormattedDate strFormattedDate = Format(DateAdd(“d”, -5, _ CDate(Me![WeekEnding])), “dddd, mmmm d, yyyy”) Me![lblTuesdayDate].Caption = strFormattedDate strFormattedDate = Format(DateAdd(“d”, -4, _ CDate(Me![WeekEnding])), “dddd, mmmm d, yyyy”) Me![lblWednesdayDate].Caption = strFormattedDate strFormattedDate = Format(DateAdd(“d”, -3, _ CDate(Me![WeekEnding])), “dddd, mmmm d, yyyy”) Me![lblThursdayDate].Caption = strFormattedDate strFormattedDate = Format(DateAdd(“d”, -2, _ CDate(Me![WeekEnding])), “dddd, mmmm d, yyyy”) Me![lblFridayDate].Caption = strFormattedDate strFormattedDate = Format(DateAdd(“d”, -1, _ CDate(Me![WeekEnding])), “dddd, mmmm d, yyyy”) Me![lblSaturdayDate].Caption = strFormattedDate strFormattedDate = Format((Me![WeekEnding]), _ “dddd, mmmm d, yyyy”) Me![lblSundayDate].Caption = strFormattedDate ErrorHandlerExit: Exit Sub ErrorHandler: MsgBox “Error No: “ & Err.Number _ & “; Description: “ & Err.Description Resume ErrorHandlerExit End Sub Additionally, the code runs a make-table query that creates a table for use in the query that is the row source of cboClientProject (see Figure 7.12); initially, the combo box’s row source is blank, because otherwise the query could not be run. The row source query is a FindUnmatched query created with the Query Wizard that excludes client/project combinations for worksheets that have already been filled out for the selected employee, so you can’t accidentally select the same one twice. 205 Working with Excel Worksheets 7 12_047026 ch07.qxp 4/2/07 9:44 PM Page 205 FIGURE 7.12 Selecting a client and project for a timesheet. If you need to modify the data on an existing timesheet, you can do this later, in the review stage, from fdlgTimesheets. After the client and project has been selected, the hours can be entered; the totals will recalculate automatically (see Figure 7.13). FIGURE 7.13 Entering hours on a timesheet. 206 Writing VBA Code to Exchange Data between Office Components Part II 12_047026 ch07.qxp 4/2/07 9:44 PM Page 206 [...]... on the Microsoft Office web site On the Databases page, you have a choice of Access 2007 or Access 2003 A choice of Access version for database templates continued 227 8 Part II Writing VBA Code to Exchange Data between Office Components continued In the Access 2007 group, you’ll see several categories Categories of Access 2007 database templates On selecting the Business category, you’ll see the templates... offers many choices for exporting Access data, but curiously, as you can see in Figure 8.1, there is no selection for exporting to Outlook Using the Collect Data Group In Access 2007, there is a new choice for interacting with Outlook: The Collect Data group on the External Data tab of the Ribbon has two buttons, one to create emails for gathering data to import into Access tables and the other to manage... 8.1 Ribbon choices for exporting Access data FIGURE 8.2 The Collect Data group on the Access Ribbon Using the Import Group to Import or Link to Outlook Data There is also a familiar choice for linking Access tables to Outlook, now updated to a selection on the More menu of the Import group on the Ribbon You can see this selection in Figure 8.3 221 8 Part II Writing VBA Code to Exchange Data between... Ribbon Selecting the Outlook Folder selection on the More menu opens a dialog box offering you three choices (shown in Figure 8 .4) : importing Outlook data into a new Access table, appending the data to an existing table, or linking the folder to a newly created Access table FIGURE 8 .4 The Import/Link selections for Outlook folders 222 Working with Outlook Items After selecting the “Link to the data source... of linking Access tables to Outlook — specifically that changes made in Access will be saved to Outlook, and vice versa — is not completely fulfilled For example, though I made changes to both the contact name and company name for a contact record in Access, only the company change was reflected back to Outlook However, both contact and company name changes in Outlook were reflected to Access Figure... Access Figure 8.9 shows the linked olContacts table 2 24 Working with Outlook Items FIGURE 8.9 A linked Contacts folder Creating a Database from a Template T o create a database from one of the new templates, first select New from the Access File menu, as shown in the following figure The New item on the Access File menu continued 225 8 Part II Writing VBA Code to Exchange Data between Office Components... Access for longer than that, you probably have calendar, contact, or task data stored in Access tables in databases that were created many Office versions ago (I have some that were originally created in Access 1.0!) In the case of contact information, there is another reason that many users prefer storing data in Access: Access is a relational database, allowing you to set up one-to-many links between companies... II Writing VBA Code to Exchange Data between Office Components As an example, the Microsoft record in my personal Access Contacts database has 30 phone numbers, many with non-standard descriptions — I couldn’t do that in Outlook! However, despite the advantages of a relational database, Outlook is undeniably attractive and convenient, so much so that you may want (or need) to export your Access contact... you have tasks or calendar items stored in an Access table (perhaps created before Office 97), you may wish to permanently move them to Outlook, which offers a superior interface for working with these types of items CROSS-REF See Chapter 11 for a detailed treatment of synchronizing a set of linked Access tables with matching Outlook contacts Exporting Access Data to Outlook Items Apart from exporting... items on the fly, as the data in your Access tables changes, using code running from event procedures or macros For example, if you have a database of project-related information, you can create project task reminders in the form of email messages filled with data from an Access table, or Outlook tasks or appointments triggered by changes in data stored in the Access tables You can use the legacy SendObject . _ xlNone .Range(“A4:F4”).MergeCells = True .Range(“A4:F4”).Borders(xlDiagonalDown).LineStyle = _ xlNone .Range(“A4:F4”).Borders(xlDiagonalUp).LineStyle = _ xlNone .Range(“A4:F4”).Borders(xlEdgeLeft).LineStyle. xlNone .Range(“A4:F4”).Borders(xlEdgeTop).LineStyle = xlNone .Range(“A4:F4”).Borders(xlEdgeRight).LineStyle = xlNone .Range(“A4:F4”).Borders(xlInsideVertical).LineStyle = _ xlNone .Range(“A1:A4”).Font.Size. & Err.Description Resume ErrorHandlerExit End Function 2 04 Writing VBA Code to Exchange Data between Office Components Part II 12_ 047 026 ch07.qxp 4/ 2/07 9 :44 PM Page 2 04 Private Sub FillDateControls() On Error