Convert Lotus 123 file to Excel XP

[fatboyjim]

I have a 540KB Lotus 123 file here I wish to open up (full of Referee's statistics)

I don't have 123, only Office XP (and 2000 and 97 if installing those will be of any help...)

Is there a program out there to convert them to me? Or do I have to find a 123 friend to save it as an Excel file?

Thanks all,

[glc]

Excel should be able to convert and open Lotus directly.

[sdkfz]

you should be fine with office, open Excel and then in the menu select:

File-->Open--> and then change the 'Files of Type' drop down in the lower left corner to the fourth option 'Lotus 1-2-3 Files' and then navigate to the location of the file.

Just remember to save the file somewhere else as soon as opened so that you have a converted (excel) format and the original (123) format (just because I am paranoid and have had weirdness happen in the past)

[fatboyjim]

Hmm, that is what I first thought

However, the file I have received is called "Referees.123" and Excel tells me "Cannot open Lotus 123 file"

This is Excel XP running on Windows 2000

Thanks,

Jim

[mairving]

You might have to stick the Office disk back in and install the filter for 123. I don't think that it is installed by default.

[fatboyjim]

Probably not applicible in my case as I usually just go Custom and install all of the options needed or not

Anyway, I'll give it a go.

On another note, it seems the file may be corrupt. For one, the .123 file has no icon (only the microsoft 'file not recognised' icon) and it is 540KB when Hotmail tells me it should be 714KB

What do you reckon? I have asked my friend to send it to me again, who knows

Jim

[mairving]

You know what. You may not be able to open it with Office XP. You should be able to open it Office 97, though. Can you get him to send it as a .csv or .txt tabl-delimited file instead?

[fatboyjim]

Thanks for the idea,.

I've asked him to send it again in 123 format already. But if that doesn't work, I'll see if it can be sent as a CSV

Thanks,

Jim

[David_Jones]

I may be well out of date here (5 years since I used Lotus 123), but the extension for 123 files was not .123 but was .wk?

Lotus 123 Version1 = .wks (I think)
Lotus 123 Version2 = .wk2 (possibly)
Lotus 123 Version3 = .wk3 (definately sure on that one)
Lotus 123 Version4 = .wk4 (sure on that too)

I wonder if the .123 file is actually in 123 format?

Also, I am sure that 123 could save a file in Excel format, so why not ask the sender to try that as well?

Ignore me if I am just out of date!

David.

[casey]

Since release 9, 9.5 & 9.6 the extention is .123

[casey]

Office XP cannot open Lotus .123 files

[casey]

I use Excel & Lotus 123 all the time, what we do is to take the lotus file and save it as an Excel .xls file. (Do the convertion from within Lotus) I know you do not have lotus on your PC, maybe a fried can help you ?
If it is not confidential you can Zip it up an mail it to me, I'll convert it and send it back asap.
Hope I'm not overstepping any rules here.

[fatboyjim]

Sure, I'll do it ASAP

Thanks for the help,

Jim

PS. Can earlier versions of Office open 123 files (as in files with extension 123?)

[casey]

Fatboyjim,
I've send the conversion off to you. Did you receive it ?

[casey]

Just tried Office 2000 Professional. would not open .123 file.
It does however open a lotus file with the .WK4 extention, so what you can do is to save the Lotus file as .wk4 (used for versions prior to release 9) instead of the default .123 and Excel will read it. Lotus will however give you a warning that you might lose some formatting.

[sdkfz]

97 has the option to open and save in 123, (I am on 97 at work and XP at home) I am surprised XP can not do this. now I will have to go home and have a look, I am intrigued

[sdkfz]

OK now I am stumped, XP does have the lotus file type, you certain the file is OK? has someone been able to open it and send it back to you?

[casey]

I opened the file in Lotus Smartsuite 9.6 and converted it to Excel.
EMailed it to Fatboyjim, but have not heard from him yet. There was nothing wrong with the file.