BtServer:Notify()

 

<< Click to Display Table of Contents >>

Navigation:  Server Classes > BtServer Class >

 

BtServer:Notify()

 

Previous pageReturn to chapter overviewNext page

 

Purpose

 

 

An event handler that responds to events of this server or related objects

 

 

 

Prototype

 

 

METHOD Notify (  kNotification, uDescription  )  CLASS BtServer

 

 

 

Argument(s)

 

 

<kNotifyName>                Identifies the event, specified as one of the following constants:

                         NOTIFYAPPEND, NOTIFYCLEARRELATION, NOTIFYCLOSE, NOTIFYCOMPLETION, NOTIFYDELETE,                                NOTIFYFIELDCHANGE, NOTIFYFILECHANGE, NOTIFYGOBOTTOM, NOTIFYGOTOP,

                         NOTIFYINTENTTOMOVE, NOTIFYRECORDCHANGE, NOTIFYRELATIONCHANGE

<uDescription>                Used only with some notification types, as described above.

 

 

 

 

Return

 

 

Unimportant except if NOTIFYINTENTTOMOVE is specified for kNotifyName. In this case, the return value is TRUE if successful; otherwise, FALSE.

 

 

 

Description

 

 

An event handler that responds to events that have occurred in methods of this server, or in other servers that are linked to this server in some way.  The standard implementation notifies all the server's clients of the event.

 

This method is at the heart of the automatic notification among linked windows and servers.

 

When certain actions are performed on a data server, the methods that perform those actions automatically call their Notify() method upon completion of the action.  The data server then sends a broadcast Notify message to all of its clients to notify them of the action.

 

This ensures that all clients (for example, data windows or data browsers) remain in sync with their underlying servers and reflect the change (for example, update a field value or add a new record).

 

Any class that is registered as a client of a server must respond intelligently to these Notify messages. In some cases, the notification may come from another object rather than from a method of the same server object.  Relations among servers, for example, cause file change notifications to be sent from the parent to the child server.

 

 

 

See Also

 

 

BtServer