With Access, if you wish to access data from another database, it typically translates your Access SQL into ODBC which is passed to the target database which in turn will re-translate it into its own SQL. A pass-through is where you write the query in the target database's SQL and Access passes that string to the target to run directly. The advantages or disadvantages of this will depend on the circumstances.
A stored procedure is typically a set of instructions which is more complex than a simple SQL statement. Where Jet is concerned this can be managed via the ODBC route. They are not really core to Jet. You have to manage them via code which is really missing the whole point of Access. My feeling is if you're into stored procedures within Jet then you should be looking at an alternative database management system.
gajussi,
To expand on BNPMikes answer, you can call any SQL DML or DDL statment from a Pass-thru, including stored procedures, Create/Alter table, etc. Nearly anything legal on the backend's command-line is acceptable via pass-thru; you can pass parameters but you can't return them.
Also, most newer ODBC drivers will translate simple JET queries--those created in Design View in the query grid with Linked Tables---into sort of 'virtual Passthru', that is, they will execute on the server--even semi complex joins. However, you'll break this rule and revert to JET processing if you use Access/vba functions or joins to local tables.
--Jim
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.