Oops, sorry, MAS 200. All of my previous post still applies if it's the standard MAS 200 version.
If it's the SQL Server version of MAS 200 you might be able to do some other stuff as well using a SQL Server ODBC driver or JDBC driver, but I've never used it so I don't know what kind of junk Sage did to the DB to lock it down. If ACT is any indication then they try to keep anything not written by Sage away.