Excel Importing -Profile Creation

[t_s]

I'm attempting to use the MDG MS Office extension to import Excel files. The Excel files have a header row that needs to be mapped. In attempting to create a 'Profile' for the import I can't get past the 'Work Sheet' selection. I've selected the Excel file (as the 'Sample Document'), making sure it's not open, but then the 'Work Sheet' list remains empty. And it won't let me go to the 'Next' step.

What am I doing wrong? Is in inappropriate to use a file the is intended to be imported as a 'Sample Document'?

Any help will be appreciated.

Thank you.

[YogaMatt]

I can't answer definitively, but it would make sense for the file to be imported to be used as a Sample when creating a profile: surely it's just reading it as an aid to creating a mapping in the (separate) profile file and therefore shouldn't need to write to the "Sample". Thus the sample could then be the source? But perhaps this isn't allowed, and could be why we're having a related problem - see this thread: http://sparxsystems.com/forums/smf/index.php/topic,30337.0.html
Let's hope we get an answer 

[t_s]

Thank you for the pointer, but I had found and read that post prior to mine.

For amusement the following is a 'sample' of the types of things (in a spreadsheet) that I need to import (into a UPDM OV-3):
Need Line | Information Exchange | IE Description | Source Node | Source Activity | Destination Node | Destination Activity | Media | Frequency

It may be useful to note that I running EA on a Mac via Crossover. I have very few problems with configuration.
The most notable the inability to code or run Visual Basic.

Cheers.

[YogaMatt]

If you're running on OSX, are you:

• also running Microsoft Office under Crossover? In which case you may encounter the same issues seen running script within Office as you do within EA;
• or running Office for Mac? In which case, have Sparx stated MDG fo Office integrates with Office for Mac?

I don't these questions help, but I'd like to understand your experience too as I use a Mac at home.

[t_s]

Yes, I discovered the error (for Mac/OSX) was that I have the MS Office applications for Mac and not Windows versions running in Crossover. Oops.