Error In Excel 2007 When Opening And Creating New Files

[csharp]

I have searched endlessly and have given up to see if I can solve this
problem on my own. I just installed the Microsoft Office Professional 2007
today and everything seems to work fine except for Excel. I went back and put
my installation cd in and again and let it do a repair if needed, I
downloaded (or whatever it is called) all critical updates as well. Anyway
when I try to open an Excel file from any of my already saved files on my
computer from before I installed this new version it automatically gives me
an error and shuts down. When I try to save a file I have created fresh it
will not save and gives me the exact same error.

I have searched for this error everywhere I can think of, but cannot find
anything to match what I am dealing with. Below is what the error says and it
comes up in the form of a pop up box.

Microsoft Visual C++ Runtime Library

Runtime Error!

Program: C\Program Files\Microsoft Office\Office12\EXCEL.EXE

R6025

-pure virtual functional call

Then it has a button to push that says OK and that is all I can do is push
ok and everything shuts down off the screen (Excel that is).

Does anyone have a clue what is doing this and how I can fix it? I am lost
at what else to do and I guess I do not know how to pick the appropriate
keywords to find the information on my own as I cannot find anything that
matches my problems and error message.

Thanks.

 

[csharp]

I forgot to mention one thing that might be of importance is that my previous
version was Microsoft Office XP version 2002. I did not know if that would
need to be known if anyone does have a solution to my problem. I was told
when purchasing this 2007 version that there would not be any problems with
my old files converting into the 2007 office programs, but that is not
happening here. Thanks in advance if anyone can help.

 

[csharp]

Okay I feel like a HUGE IDIOT here. Never mind to my question. After sitting
here and searching literally all day as to what my problem could be I ended
up finding a fix on my own after I wrote these messages. Sorry to take up
space on the board.