Trouble with Upgrade to Windows XP with works Calender File

I upgraded my computer from windows 98SE to Windows XP. When trying to
open a calender created in Works with the 98SE OS previous to
up-grading the calender wont ope and says it a .vcs file. It seems to
think that Outlook can open this but when you do an open with it just
opens Outlook, Outlook Express that is. How do I open this file?

Thanks, Lane

Louie LaRue wrote:

> I upgraded my computer from windows 98SE to Windows XP. When trying
> to open a calender created in Works with the 98SE OS previous to
> up-grading the calender wont ope and says it a .vcs file. It seems to
> think that Outlook can open this but when you do an open with it just
> opens Outlook, Outlook Express that is. How do I open this file?
>
> Thanks, Lane

Do you have Works installed? OE can't open a calendar file. OE is an
email program and has no calendaring capabilities. Outlook is a
full-featured email/calendaring program that is part of MS Office.

Check with the experts in one of the Works newsgroups. Here's a list of
all the MS newsgroups so you can find the one right for your question:

http://aumha.org/nntp.htm

Malke
--
Elephant Boy Computers
www.elephantboycomputers.com
"Don't Panic!"
MS-MVP Windows - Shell/User

Louie LaRue wrote:

> I upgraded my computer from windows 98SE to Windows XP. When trying
> to open a calender created in Works with the 98SE OS previous to
> up-grading the calender wont ope and says it a .vcs file. It seems to
> think that Outlook can open this but when you do an open with it just
> opens Outlook, Outlook Express that is.


Do not mix up Outlook and Outlook Express. They are two very different
programs with different sets of capabilities.


> How do I open this file?


I don't use vcs files, but clearly you need a program that knows what to do
with them. Outlook Express has no calendar functionality, so it's not what
you need. Outlook can handle vcs files, and if Microsoft Works created the
file, obviously it can too. Presumably either of those would work, and I
believe there are other choices too, although I don't know what they are.

--
Ken Blake - Microsoft MVP Windows: Shell/User
Please reply to the newsgroup