Skip to main content

Manage SQL Server scripts from MS Access 2010


The application was not fully tested with multiple SQL Servers. I did not have access to them. Feel free to alter as needed.

This application allows the user to manage SQL Server scripts. It also allows the user to place SQL Server .SQL scripts in a "Run Once" Windows folder or in a general "Run Whenever" Windows folder.

The scripts can be prioritized so they run in a specific order, if necessary.

The program works with Windows Logon as well as SQL Server Logon.

Be careful running the Once Only files. If you delete them from the Audits they may re-run.

I am going to change this to have a separate Audit table for the Once Only files.

The code was written using MS Access 2010 but I tested it using MS Access 2007 and it seems to work as well. I did not do an exhausting test in MS Access 2007.

There is another program called TextMaker Viewer 2010 or later (The file size exceeds this sites limits) that should be installed. It allows the user to view the Log Files from the program. The log files are created in Windows Folders. You can get it at This is a FREE program.

This program is activated when you click the Results button on the main scree. Change the File Types to All Files. This is where you see if there were any issues running the system. Since I am using a .Bat file to run the SQL Scripts, I cannot get results back to the Access program.

Uncheck ALL associations so this program does not become the main program to view them unless you want it to be.

I would have included it in the zip file but then the file would exceed the 2 MB limit.

There is a user document file included in the zip file.

Note: Due to the size or complexity of this submission, the author has submitted it as a .zip file to shorten your download time. After downloading it, you will need a program like Winzip to decompress it.

Virus note: All files are scanned once-a-day by for viruses, but new viruses come out every day, so no prevention program can catch 100% of them.


1. Re-scan downloaded files using your personal virus checker before using it.
2. NEVER, EVER run compiled files (.exe's, .ocx's, .dll's etc.)--only run source code.

Add new comment

This question is for testing whether or not you are a human visitor and to prevent automated spam submissions.