Girish Mohata wrote: ... > 3) In developing a data-driven software, my > attitude would be to run the business logic on the > server using triggers and procedures rather than > coding it in Visual Basic. In other words if i > wish to insert a record, i would do it by calling > a stored procedure and passing data values to it > from VB, rather than writing an SQL statement > through VB. Please advise on this. Any > comments/suggestions/experiences would be much > helpful.
To have a stored proc with just one SQL-statement in it is (in my opinion) overkill. If nothing else (no calculation of data, inserting/updating of other tables,selecting,...) is done, just inserting one row, there is no need, but overhead, to do this in a stored proc. With the insert and with the dbproc you have to fill the parameters and you have to check the error afterwards, there is no difference. Elke SAP Labs Berlin _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
