...got a repository module acting up on one of my hidden development pages; I can no longer view the page without triggering an application error related to the repository module.  Therefore, I am wondering how we can remove a module without viewing that page?  Would I go into the db, find the respective table and remove it? Where would I look exactly?

I have the page hidden, so no-go on logging is as a non-host. Also, I am unable to view the source and get the module ID, as the source is showing the application error only.  :(

...only thing I can glean from the error is that the module causing the error is, in fact, the repository dashboard:

ReferenceException: Object reference not set to an instance of an object.
   DotNetNuke.Modules.Repository.RepositoryDashboard.FindRepository() +61
   DotNetNuke.Modules.Repository.RepositoryDashboard.Page_Load(Object sender, EventArgs e) +139
   System.Web.UI.Control.OnLoad(EventArgs e) +99
   System.Web.UI.Control.LoadRecursive() +47
   System.Web.UI.Control.LoadRecursive() +131
   System.Web.UI.Control.LoadRecursive() +131
   System.Web.UI.Control.LoadRecursive() +131
   System.Web.UI.Control.LoadRecursive() +131
   System.Web.UI.Control.LoadRecursive() +131
   System.Web.UI.Control.LoadRecursive() +131
   System.Web.UI.Control.LoadRecursive() +131
   System.Web.UI.Control.LoadRecursive() +131
   System.Web.UI.Control.LoadRecursive() +131
   System.Web.UI.Control.LoadRecursive() +131
   System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1061

PageLoadException: Object reference not set to an instance of an object.
   DotNetNuke.Services.Exceptions.Exceptions.ProcessPageLoadException(Exception exc, String URL) +363
   DotNetNuke.Framework.PageBase.Page_Error(Object Source, EventArgs e) +484
   System.Web.UI.TemplateControl.OnError(EventArgs e) +105
   System.Web.UI.Page.HandleError(Exception e) +73
   System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +6944
   System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +154
   System.Web.UI.Page.ProcessRequest() +86
   System.Web.UI.Page.ProcessRequestWithNoAssert(HttpContext context) +18
   System.Web.UI.Page.ProcessRequest(HttpContext context) +49
   ASP.default_aspx.ProcessRequest(HttpContext context) +4
   System.Web.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +154
   System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +64

Yea, I am holding out a bit longer, but that's my standard fix, that's for sure.  It's just my play page where I tweak stuff before moving live, but there are a couple of things on there I would like to save....but if not, I'll do as you suggest and just start a new development page and write this one off as a lesson learned.  :)