Difference between revisions of "DBC CLOSEDATA"
Yvonne.milne (Talk | contribs) |
Yvonne.milne (Talk | contribs) |
||
| Line 36: | Line 36: | ||
|} | |} | ||
| − | Programs associated with database events should reside in the database's directory. | + | Programs associated with database events should reside in the database's directory. These can be created and modified from the Events tab in the Data Workspace when a database is open. |
==Example== | ==Example== | ||
Revision as of 05:53, 17 October 2016
Contents
Purpose
Database event triggered by the closure of a database
Syntax
PROCEDURE dbc_CloseData(<expC>,<expL1>)
// Commands
ENDPROC | RETURN [<expL2>]
or
PROCEDURE dbc_CloseData
LPARAMETERS [<expC>,<expL1>]
// Commands
ENDPROC | RETURN [<expL2>]
See Also
ADATABASES(), ALTER TABLE, ADD TABLE, ALTER INDEX, CLOSE DATABASES, CLOSE TABLES, COMPILE DATABASE, CREATE DATABASE, CREATE TABLE, CREATE INDEX, CREATE VIEW, DATABASE(), Database Events, DBUSED(), DISPLAY DATABASE, DISPLAY INDEXES, DISPLAY TABLES, DROP DATABASE, DROP INDEX, DROP TABLE, GETENV(), LIST DATABASE, LIST INDEXES, LIST TABLES, OPEN DATABASE, PACK DATABASE, REBUILD DATABASE, REINDEX DATABASE, SET AUTOCATALOG, SET EXCLUSIVE, USE
Description
The DBC_CLOSEDATA database event is triggered by the closure of a database. The associated code is run before the database is actually closed. Databases are closed using the CLOSE DATABASES command.
| Event | Description |
|---|---|
| <expC> | The database name |
| <expL1> | Specifies whether the ALL keyword was included on the CLOSE DATABASES, .T. or not, .F. |
| <expL2> | If the dbc_closedata procedure returns .F., the database is not closed, if .T., the close operation continues |
Programs associated with database events should reside in the database's directory. These can be created and modified from the Events tab in the Data Workspace when a database is open.
Example
procedure dbc_closedata lparameters cName, lAll close procedures return
