Problems importing external data with Mac version

I can imagine you're getting tired of hearing from me, and, believe me, I'm getting tired of writing. I'm attempting to import an excel spreadsheet to the Mac version of ebase, and can't.

In step 2 of Import External Data, I first get this message:

"(file name)" could not be opened. (Error)

When I clice OK, I get this message:

An error occurred while executing the 'Nav Wizard Import from Source and Next' script in the ImportExternal.200 file. Script will not continue. Error code 802.

I can import this same excel spreadsheet into the PC ebase version without a hitch. I've tried numerous things on the Mac side: I created a brand new test file in the newest version of Excel for Macs. I saved the file as older versions of Excel for Macs. I've imported the file from different places on my hard drive/desktop. But I keep getting the same error message.

Thanks, Lisa

Importing issue

Hi Lisa, no problem with writing in issues. It's a matter of setting up and learning a powerful software tool (ebase) that can help your NPO. It takes time, experience, reading the manuals, and some occasional help, which is what the forums, listservs, and available for hire ebase consultants are for.
I've just tested an Excel import file using the same Mac installed software I believe you are using and it went without a hitch.

What are you saving the Excel files as (file type) ?
Are you saving these Excel files as .csv - if not, open your Excel files, go to Save As, save as Comma Separated csv and try the import again.

Best - Tim Leed
ebase TAC member and ebase Consultant

New Importing Issue

I was attempting to import an .xls file (the standard extension for an Excel file, right?), but as instructed, I've saved the file as a .cvs file, and now the Mac version of ebase will open the file, but it isn't allowing me to view by "matching names." I've carefully matched up all of my Excel fields to ebase's fields. Can't I use a standard .xls Excel file with the Mac version so that it will recognize my fields names in the first row? Do I have to manually match all my files names?? That's a pain.

I do realize that ebase is a powerful tool, and I've studied the manual, read through the old forums, and also set up a successful test database using our organization's real data with the PC version of ebase, including log codes that seem to work for us.

The ultimate end-user of my database is Mac-based and because I've got a PC, I thought I could do all the set up/data clean-up on a PC and then convert it to a Mac version, but it's turning out to be a pain at every step. I can't even download the ebase program and open it without help, let alone import the file quickly and easily. Are there lots of small special issues with the Mac version? I'm really afraid of what's going to happen down the road.

Sorry, but I am frustrated.

Thanks for your help, Lisa

Importing issue resolved

Lisa, thanks for the update.
If you are going to be doing repeated imports from a specific data source often, you can save the configuration setup so you don't have to rematch up the fields each time. (See the manual.) There are some differences in the way ANY/EVERY FileMaker based solution works on Macs vs PC's and PC's vs Mac's. If you are going to support the installs, you'll have to learn these, and it does take time and experience. We have users that adore ebase on Mac's and think it's funky on a PC, and the other way around. It is one of the super things about ebase that it is a cross-platform solution and therefore is available to a wide array of nonprofit organizations to use.
Keep the questions coming... there's lot's of help here at ebase!

Best, Tim

Hello Lisa,

Hello Lisa,

I work on a Mac (at work and at home) and have not had such a problem with an .xls file; I do weekly imports into ebase.

I just tested a .csv file and got the same result of not being able to use matching names (grayed out). I think its because a .csv file does not believe it has field names. However, when I changed the same test file to an Excel spreadsheet, I could match names. You could also try saving the file as a merge (.mer); this type of file does/should keep field names.

Caveat: to be a true test I should be using the runtime, but my Mac at home is old enough that I can't open the most recent runtime version.

Beth Hynes