>>If the table is free, you can still use the same concept, you just have to >handle it manually in code from everywhere that records get added to the >table, and you can't use a dbc's stores procedure. > >just a side note - >you can use the DBC stored procedures provided you have SET DATABASE TO the DBC >if a DBC is the current database you can call its SPs directly Arnon, Are you saying a stored procedure runs when called from a web page (that isn't in VFP). I don't understand how can the stored can run since there isn't an interpretor running. Let's say you have (in a VB Script in an Active Server Page): SQL_CLUASE = 'INSERT INTO MyDBF ("comment") VALUES ("ABC")' ' connection=CreateObject("adoDB.Server") blah, blah, blah connection.EXECUTE(sql_clause) If there is a insert trigger in the DBC, are you saying that the code will execute? Even without VFP installed on the server? (Just the ODBC driver)