Using Microsoft Script Editor for Data Access Pages - Client Objects and methods
(Page 5 of 5 )
Fig.13 shows even more possibilities. For each of the objects, you can access all the associated events that you may ask them to do. You have complete flexibility to use DHTML to your hearts content.
Events raised by Client Objects
Fig.13
Fig.14 shows the default client scripts that will be present in all data access pages as well as the Window object -- the container object. Sure enough you can access all events. The design of this interface has left very little that you can add to. Well, wait for the next article regarding the OWC.
Default Client Scripts and Window Object
Fig.14
Fig. 15 shows how you may arrange to see the script. Now how do you access the code? It's easy. In the Microsoft Script Editor's page go to view and click on Show Script Only... and you will see the script as shown. When you choose any of the client object's events, for example, the click event to one of the command buttons, that code will be appended to the default template script shown here. I'll tell you more about it in the next tutorial.
Fig.15
Summary
This tutorial has detailed how to prepare to script a Data Access Page. The next tutorial will expand upon this tutorial and show how you may effectively script a page.
| DISCLAIMER: The content provided in this article is not warranted or guaranteed by Developer Shed, Inc. The content provided is intended for entertainment and/or educational purposes in order to introduce to the reader key ideas, concepts, and/or product reviews. As such it is incumbent upon the reader to employ real-world tactics for security and implementation of best practices. We are not liable for any negative consequences that may result from implementing any information covered in our articles or tutorials. If this is a hardware review, it is not recommended to open and/or modify your hardware. |
/ 22 
