If you can get a "clean" sample of the file, you can upload it to a website that specializes in scanning virus samples. A google should yield a list of sites that do this.
I'd try getting a liveboot CD for Linux and access the file that way, as Linux doesn't execute Windows executables (as long as it's not running WINE) and OpenOffice shouldn't support any oddball macros in Office documents. Even if it did, the payload should be adequately confused by Linux conventions to render it immune.
Then I'd get the file, upload it to the website, and that should give you some idea of what you're dealing with.
This isn't like the good old days where a virus was a virus was a virus. Today each vendor names viruses with their own conventions, and any slight change is suddenly a new virus (we catch 18 billion viruses compared to our competitor! We don't mention that 17.9 billion of them just have a different typo!)
If you're not familiar with Linux, you may be able to find someone with some experience with it to assist. Linux has been a real gift for troubleshooting issues like this for us; it's like having a heavy environmental cleansuit for handling malware that would cripple a Windows workstation if there's an "accident" while trying to analyze the situation.
A Macintosh onsite may also be able to handle the document in a way that will allow you to upload it to an online scanner as well, as long as you don't have an integrated Windows emulator/virtualizer installed that runs a virtualized Windows session by clicking on an executable, and if your document is using some form of macro and you have Office installed I don't know if it'll try running certain macros or not. Again, though, it should be confused by the platform differences anyway...unless you have WINE or a virtualizer integrated so that you accidentally infect your virtualized environment.