>Hmmm, this is probably not the best way to get around this (hopefully someone with more experience can give you a better answer). But here is an idea. What about creating a bogus bogus table with say, one field. On this table you could put an insert trigger that holds the code that your stored procedure currenlty has. Change your stored procedure to simply insert a value into your bogus table and then return. This will cause the trigger to fire and run your code while at the same time returning control to your application. Just an idea...
>
>

---

This is how we do with the rest; we have an interface log table in Oracle that triggers Oracle SP and our VFP app procedures. This is just one "very special" SP that they require me to initiate.