Importing Appleworks Database

Appreciate the quick reply WWJD. Appleworks does not allow saving in any format except ASCII, unless you wish to export as something even more ancient than Appleworks like Claris Works. As I recall, I created these database files in Filemaker long before Pro, then we got Works, then AppleWorks. It's been so many years and so many machines I'm a bit fuzzy.

I purchased IWorks with the apparently misguided understanding it was the "upgrade and replacement" for Appleworks, which I believe dates from OS 8 or earlier. IWorks is indeed powerful compared to Appleworks, but the ability for IWorks to update or import ALL Appleworks files seems like a no-brainer to me.

Though we never pretended Appleworks was "high end" in any features, it was the generic workhorse of Apple applications. It it's not like the Apple engineers to leave us hanging like this, with no alternatives other than purchasing non-Apple software to translate Apple files.

Fortunately, Appleworks seems to run fine on my new 8-core Mac Pro, so all is not lost. Come on Apple, how bout complete file translation from Appleworks to IWorks in the next update?

Very generous offer to translate my 5-meg database documents WWJD! With 25 columns and over 25,000 lines, one missed comma or character could render the entire file useless gibberish. These huge files have been very subject to corruption and failure over the years. Though I'm avid about my backups, it isn't unusual for me to be forced to revert, and renter many lines of data between saves.

Generally the data in these files isn't particularly "sensitive," though in some critical cases it simply can't be shared under any circumstances. I'm sure you understand.

I'm a staunch believer in "if it ain't broke, don't fix it." Since Appleworks still runs on my Mac Pro under Safari, there's little advantage in upgrading these files to IWorks. I can survive for quite some time in the hopes the Apple engineers will hear our pleas for IWorks to translate Appleworks database, drawing, and painting documents.

I'm not a user of Appleworks Presentation, but if IWorks can't update those files either, then the IWorks engineers should truly hang their heads in shame...

In searching the various discussion threads, there are viable workarounds to at least partially enable the upgrading of some Appleworks files to IWorks through existing Apple avenues. It's truly unfortunate we have no choice but to revert to third party software options to upgrade Apple files.

Apple, hear our pleas!

WWJD, you've been great! I'd like to mark this question "resolved," and close the thread, but I'll allow it to hang open a while longer in the hope it attracts a bit more attention.

This is interesting wolfhill! I have Excel, but I'm a bit confused. How did you get your files from Appleworks into Excel? My Excel OSX version won't read anything non-Microsoft. My Appleworks won't save in any other formats except ASCII and Claris Works. I see no options to create csv files.

My original files were created on my 16 MHZ FatMac (Yep, I'm a dinosaur) and have been upgraded through IIci and G3 to my current Mac Pro Leopard.

Are you saying I need slide over to the dark side, and fire up my PC in Windows Excel to enable the translation to IWorks?

Now I'm curious WWJD, if AppleWorks database files have "features and functions" unavailable to spreadsheets, why did Apple abandon databases and leave so many users with such limited avenues for software support?

Yow wolfhill, that sounds mind-numbing. I have files that date from my Apple+ too! We are two dinosaurs!

If I understand you correctly, key to getting your files to translate was Claris Works being able to save them as DBF or Excel. I can't run Claris Works anymore, so I may be doomed. I'm right back to purchasing Filemaker Pro, which is where this thread started.

Am I missing something else here?

My thanks to you all. I guess this one is solved.