It is kind of a bad idea to put your main SQL code in a module: if your database requirements change you will need to recompile and redistribute your app, which can become a major headache. You are better off using views and stored procedures on the SQL server itself, especially for core components that will get called repeatedly.
If you do chose to go with using app-side SQL,
USE PARAMETERIZED QUERIES. A piece of code like
"DELETE FROM Leagues Where LeagueName = '" & myLeague & "'"
will get compiled and stored separately for EACH different
myLeague
. This ends up taking a lot of cycles: time to sort through the dozens of other
DELETE FROM Leagues
with different names, time to compile yet another variation, time to store that new version in memory in case it gets used again, and time to clear out the compiled cache when it gets full.
Instead, use
"DELETE FROM Leagues Where LeagueName = @LeagueName"
and pass your parameter in with a
SqlParameter
object. Your SQL Server will have only one variant to compile, and will use that one variant over and over again.