How to call a mysql stored procedure from access without using pass through query

I have a stored procedure that creates table in mysql backend. How do I call this procedure without using pass through query.
LVL 16
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Can you please explain what you mean by "without using pass through query"
Explain the question.. The context is not clear
SheilsAuthor Commented:
Currently I have a pass through query call qrunproc with the following sql:

 call CreateTblApplicationSearch

where CreateTblApplicationSearch is the name of the stored procedure

To run the procedure I use the following code

Currentdb.Execute qrunproc

The problem is that this method activates the pass through query warning.  Deactivating the warning on each computer on the network is not an option
Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

SheilsAuthor Commented:
I am trying to call a mysql stored procedure from an ms access front end
I don't believe you can.
why do you not want to use a pass through?
I use pass throughs heavily and never saw a "pass through" specific warning. if you're talking about the action query warning you can disable that temporarily by issuing a docmd.setwarnings false before the db.execute and docmd.setwarnings true after
Leigh PurvisDatabase DeveloperCommented:
Indeed, SetWarnings doesn't affect the DAO methods of query execution.
Only the Access DoCmd object methods OpenQuery and RunSQL.
Executing the passthrough via either DAO or ADO object models would only raise an error (or, conceivably, a message passed back from the server is your code responds in that way).
Are you really using:
CurrentDb.Execute "qrunproc"

And you get the same message with:
CurrentProject.Connection.Execute "EXEC qrunproc"

What message exactly?

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
I said you can't.  The two answerers both said something unrelated to the question.  Care to explain?
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Access

From novice to tech pro — start learning today.