We have a SQL Server 2008 database that has stored procedures to handle reads/writes/etc. These procedures are used by a variety of applications internally.
The need ha
I would recommend that you create a simple Webpart that does the edit. You will have an easier time finding someone who can do C# to a database than vba. Coding a very rough webpart to any coding in this manner is pretty easy.
There are also plenty of coding samples for C# and webparts available.
You also have the benefit of keeping the code on the server without potentially exposing username/password combinations in clear text within an office document.
This approach also enables you to smoothly improve the "quality" of the solution if it becomes more mission critical over time.
It does sound that you are following a scenario covered nicely by this example