If you mean "spot disable" the trigger from outside of the ORACLE program, you can't. ORACLE triggers don't know beans about VB or VBA, or any other ODBC caller.
From the outside, ORACLE is (and is SUPPOSED to be) a "black box." You give it a command, it does what it is told to do. And if someone told it to apply triggers in certain cases, it does that behind the scenes. To you on the outside it OUGHT to be transparent and invisible. So my question is, "What trigger?"
You might as well ask for a way to stop Access from incrementing an Autonumber field when creating a new record. That is the same class of request.
If you mean "permanently disable" the trigger, you have to send some SQL to ORACLE that has the effect of nullifying the trigger. But from Access this would be a waste of time. If you are the administrator of the ORACLE instance, you could do this from ORACLE's SQLplus interface, which works just fine.
If you are doing this any other way, dollars to donuts says you are trying to do something you shouldn't do. Triggers are put in a database for a reason. If you have a reason to bypass the trigger, talk with your ORACLE DBA. S/he might have some helpful comments, observations, and suggestions.
