FiveTech Software tech support forums

Code: Select all  Expand view

Structure for database: C:\db3\db3p\ss\conta1\datos\coopmad\logact.dbf
Number of data records:      29
Date of last update   : 04/14/10
Field  Field Name  Type       Width    Dec
    1  IDENTIF     Character      4
    2  FECHAC      Date           8
    3  HORA        Character     10
    4  OPC         Character     60
** Total **                      83

jllinas wrote:Ariel: ¿Como obtengo la identificacion de la terminal que ejecutó la acción?

Code: Select all  Expand view

#pragma BEGINDUMP
#include <tchar.h>
#include <hbapi.h>
#include <windows.h>
#define MAX_USER_NAME 128

HB_FUNC( CCOMPUTERNAME )
{
   DWORD lwMax = MAX_COMPUTERNAME_LENGTH ;
   TCHAR hostname[ MAX_COMPUTERNAME_LENGTH + 1 ] ;
   GetComputerName( hostname, &lwMax ) ;
   hb_retc( hostname ) ;
}

HB_FUNC( CWINUSERNAME )
{
   TCHAR cusername[ MAX_USER_NAME + 1 ] ;
   DWORD wLen = MAX_USER_NAME ;
   GetUserName( cusername, &wLen ) ;
   hb_retc( cusername ) ;
}
#pragma ENDDUMP
 

Code: Select all  Expand view

? netname()
? netname(.t.)

A trigger is a piece of code (similar to a stored procedure) that is executed on the server. Triggers differ from stored procedures because triggers are not called by the client, but instead are executed automatically in response to an insert, update, or delete operation.
Triggers are supported for both SQL and navigational update operations. Throughout this documentation the update operations will be specified using uppercase notation (for example, INSERT), but this does not imply an SQL-only limitation.

When a trigger is "fired" it contains some state information, which can be used inside the body of the trigger. Two in-memory tables are available inside a trigger; a __new table and an __old table. The __new table contains new field values that were, or are about to be, inserted into the table. The __old table contains old field values for the record in question.
Triggers can provide a very powerful means to maintain business rules inside of a database.
Triggers can be defined for any supported table type, and are not limited to the proprietary ADT format.

Both the Advantage Database Server and the Advantage Local Server support triggers. Implicit Transactions are the only trigger functionality that differ depending on server type.
Trigger support is a server-side feature. Any Advantage client version 6.0 or greater capable of opening a dictionary-bound table can utilize triggers. This can be beneficial if you want to add trigger support to your application, but don’t want to upgrade your client applications. Only the database server needs to be upgraded (to Advantage version 7.0 or greater) in order to start using triggers.