[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: New AppleWorks vs Classic AppleWorks
In article <mfumu-DB7D5F.07474005032003@news.alphalink.com.au>, Bill
Robbins <mfumu@alphalink.com.au> wrote:
> In article
> <declan_macleoid-7E740E.22485803032003@news-server.nc.rr.com>,
> Declan MacLeod <declan_macleoid@hotmail.com> wrote:
>
> > My memory is failing me on this. I've created a spreadsheet in
> > AppleWorks 6.2.4 under OS X and saved it as a tab-delineated text file.
> > I've transferred it to my IIgs hard disk. Is there a way to import it
> > into the spreadsheet module of Classic Appleworks (v5.0)?
>
> (Mac) Appleworks 6 will allow you to save a spreadsheet in ASCII format.
> This is a TAB delimited file (TABs between fields, RETURNs at the end of
> each record). Now it's been quite a while since I have used AppleWorks
> 5 (Classic), but I'm quite sure it will allow you to import such a file
> as a spreadsheet, using the TAB/RETURN delimiting to sort the file
> properly. Of course you WILL loose any fancy features, but this would
> probably happen no matter what conversion scheme you used.
It works with ClarisWorks 4 and AppleWorks 3.0. ALso, you might wnat to
see if the DIF format is available on AW6. It will let you retain a bit
more of the features than ASCII will.
Unfortunetly, there is one final problem. Versions of the Mac OS higher
than 7 have this compulsive need to attatch empty resource forks to any
file they encounter. Even if you save the file directly to a ProDOS disk.
So, you will need to use something to strip the resource forks. Saving to
a Macintosh disk and running it through A2FX or HFSLink works quite well,
but newer Macintoshes don't even have disk drives.