that seems like the annoyed outburst of an overworked technical author, but whenever you produce Entry programs for some others to use, you might be pretty much on the hook to write the Benefit for them. month, we featured the “How to synchronize combo boxes" template, and commenter Shairal was interested to know how the "Click to see details" reports were done. think this is a pretty clever way to add Assistance to your Entry programs.To summarize the system, the links (actually command buttons formatted to look like hyperlinks) open a simple Access report,
win 7 professional update key, and the report is bound to a table that contains all of your Support topics. The correct topic is determined by filtering the report so that it displays the appropriate record from the table. That filtering is done by the OpenReport action of the embedded macro in each command button. Here’s how to do it: step is to create the table that contains the Assistance content. In the template, this is named tblExplanations, and in Design View,
office 2007 Pro Plus update key, it looks like this: selected the Explanation field so that you can see the Text Format property is set to Rich Text. This field contains the body of the Allow topic, so you want to be able to add bolding, underlines, and so on. Once you create this table, (or better yet, just import this table’s structure into your own database), you can fill it in with your “assistance content”, as we tech writers call it: each row, type a unique keyword or phrase in the Source field, which you will use later to filter the report as you run it. For example, if the topic is about adding employees, type something like “Adding Employees” or “AddEmp”. step is to create the report. In the template, this is called rptExplanations. You might just want to import this from the template into your own database to save yourself the trouble of recreating it,
office 2010 generator key sale, but it’s very simple to create. Here’s what it looks like in Design View: don’t really need the Source field to be displayed on this report, but it’s included here for your reference. As long as you have the Title and Explanation fields in the Detail section, you’re good to go. Also, be sure the Explanation text box is set to display Rich Text,
office Enterprise 2007 generator key, so that your formatting comes through. step is to sprinkle command buttons throughout your application where they are needed, so your users can click them to view the Support topics. Here’s a screenshot of the properties for one of the command buttons in the template: On Click event contains an embedded macro. To create an embedded macro: Click the property box, and then click the Establish button […]. In the Choose Builder dialog box, click Macro Builder, and then click OK. Create the macro, as shown below. Click Close, and when asked if you want to save the changes and update the property, click Yes. of the macros from the template: Where Condition argument of the OpenReport macro action is where you link the button to the correct topic. In this example, circled above, the filter is “VBA Code”. This makes the report display only the topic that contains that string in the Source field. that this example might a bit confusing because of the string “VBA Code”—that’s just because the Support topic is about using VBA code, so that’s what was chosen as the key phrase for the Source field. As mentioned in an earlier example, if the topic were about adding new employees to your database, you might use a keyword such as “AddEmp”, and the Where Condition argument would look like this: as you add more features to your application,
genuine microsoft windows 7 activation, just add more rows to tblExplanations, and more command buttons at strategic locations in your application. You can even create a form based on tblExplanations to make it easier to publish new topics. Posted by Chris Downs, writer, Access IW Content Team