This article describes how to create a custom hit counter that will not be visible in your page, and how to obtain the hit count information from the Web page.
Inserting an Invisible Counter
To insert an invisible counter, use one of the following methods:
Format the Hit Counter as "Hidden":
On the Insert menu, point to Component, click Hit Counter, and then click Finish.
Select your options, and then click OK.
Highlight the Hit Counter on your page, click the Format menu, and then click Font.
Check the Hidden box, and then click OK.
Create an "Invisible" Custom Image:
Use an image editor, such as Microsoft Image Composer, to create the image you want to use for the hit counter. This could be either a transparent image, an image with the same color as the background of the page, or an image with a width and height of 1-pixel.For additional information on creating a custom hit counter image, click the article number below to view the article in the Microsoft Knowledge Base:
295224 HOW TO: Create a Custom Image for the Hit Counter Using FrontPage 2002
Save the image into the images folder of your FrontPage Web.
On the Insert menu, point to Component, and then click Hit Counter.
In the Hit Counter Properties dialog box, click Custom Picture. Type images/(image name) in the window, where (image name) is the file name of the image you created in step one.
To retrieve the hit count information front the Web, follow these steps:
Open your Web in FrontPage.
On the Tools menu, click Web Settings.
On the Advanced tab, click to select the Show documents in hidden directories check box. Click Apply to refresh the Web.
In Folders view, open the _private folder.
Right-click the file named (file name).cnt, where (file name) refers to the page where you inserted the hit counter, then click Open With.
Select Text Editor (notepad.exe), then click OK. Your hit counter statistics will be displayed in Notepad.
Microsoft provides programming examples for illustration only, without warranty either expressed or implied. This includes, but is not limited to, the implied warranties of merchantability or fitness for a particular purpose. This article assumes that you are familiar with the programming language that is being demonstrated and with the tools that are used to create and to debug procedures. Microsoft support engineers can help explain the functionality of a particular procedure, but they will not modify these examples to provide added functionality or construct procedures to meet your specific requirements. back to the top