XP Pro SP2, w/auto updates enabled

I'm trying to import messages from OE6 into Office 2003 Outlook,
after up upgrade to both IE7 (from IE6) and Office 2003 (from Office
2000, without Outlook installed).

The .dbx files are very large (e.g., inbox.dbx, nearly 1GB) and there
are a lot of them.

Outlook has been hour-glassed for almost 9 hours. msimn.exe has been
as high as 28MB, although it's around 13MB now.

How can I tell if things are going well?

Ideally you should export from OE to OL.
Not knowing much about OE I'd have thought your inbox.dbx was overly large
for correct operation of OE

"Richard Eich" wrote in message
.. .
XP Pro SP2, w/auto updates enabled

I'm trying to import messages from OE6 into Office 2003 Outlook,
after up upgrade to both IE7 (from IE6) and Office 2003 (from Office
2000, without Outlook installed).

The .dbx files are very large (e.g., inbox.dbx, nearly 1GB) and there
are a lot of them.

Outlook has been hour-glassed for almost 9 hours. msimn.exe has been
as high as 28MB, although it's around 13MB now.

How can I tell if things are going well?

address@invalid wrote...
Ideally you should export from OE to OL.
Not knowing much about OE I'd have thought your inbox.dbx was overly large
for correct operation of OE

With me readily assuming all the risk here, how much harm could I do
to kill OL, kill msimn.exe if need be, and try to export from OE
rather than import?

(Yes, the file sizes have been a little problematic.)

"Richard Eich" wrote in message
XP Pro SP2, w/auto updates enabled

I'm trying to import messages from OE6 into Office 2003 Outlook,
after up upgrade to both IE7 (from IE6) and Office 2003 (from Office
2000, without Outlook installed).

The .dbx files are very large (e.g., inbox.dbx, nearly 1GB) and there
are a lot of them.

Outlook has been hour-glassed for almost 9 hours. msimn.exe has been
as high as 28MB, although it's around 13MB now.

How can I tell if things are going well?

Remember, you must be using a unicode .pst file in Outlook 2003 to import anything over 1.87 gigs of information. Otherwise, Outlook will hurl.

--�
Milly Staples [MVP - Outlook]

Post all replies to the group to keep the discussion intact. All
unsolicited mail sent to my personal account will be deleted without
reading.

After furious head scratching, Richard Eich asked:

| address@invalid wrote...
|| Ideally you should export from OE to OL.
|| Not knowing much about OE I'd have thought your inbox.dbx was overly
|| large for correct operation of OE
|
| With me readily assuming all the risk here, how much harm could I do
| to kill OL, kill msimn.exe if need be, and try to export from OE
| rather than import?
|
| (Yes, the file sizes have been a little problematic.)
|
|| "Richard Eich" wrote in message
||| XP Pro SP2, w/auto updates enabled
|||
||| I'm trying to import messages from OE6 into Office 2003 Outlook,
||| after up upgrade to both IE7 (from IE6) and Office 2003 (from Office
||| 2000, without Outlook installed).
|||
||| The .dbx files are very large (e.g., inbox.dbx, nearly 1GB) and
||| there are a lot of them.
|||
||| Outlook has been hour-glassed for almost 9 hours. msimn.exe has
||| been as high as 28MB, although it's around 13MB now.
|||
||| How can I tell if things are going well?

wrote...
Remember, you must be using a unicode .pst file in Outlook 2003 to import anything over 1.87 gigs of information. Otherwise, Outlook will hurl.

Funny you mention that -- that's exactly what happened.

Two questions, to which a URL or the right search words will help me
STFW:

1) How do I establish a unicode *.pst prior to import?

2) I have multiple OE identities. Does OL 2003 support that?

Thanks very much.


--?
Milly Staples [MVP - Outlook]

Post all replies to the group to keep the discussion intact. All
unsolicited mail sent to my personal account will be deleted without
reading.

After furious head scratching, Richard Eich asked:

| address@invalid wrote...
|| Ideally you should export from OE to OL.
|| Not knowing much about OE I'd have thought your inbox.dbx was overly
|| large for correct operation of OE
|
| With me readily assuming all the risk here, how much harm could I do
| to kill OL, kill msimn.exe if need be, and try to export from OE
| rather than import?
|
| (Yes, the file sizes have been a little problematic.)
|
|| "Richard Eich" wrote in message
||| XP Pro SP2, w/auto updates enabled
|||
||| I'm trying to import messages from OE6 into Office 2003 Outlook,
||| after up upgrade to both IE7 (from IE6) and Office 2003 (from Office
||| 2000, without Outlook installed).
|||
||| The .dbx files are very large (e.g., inbox.dbx, nearly 1GB) and
||| there are a lot of them.
|||
||| Outlook has been hour-glassed for almost 9 hours. msimn.exe has
||| been as high as 28MB, although it's around 13MB now.
|||
||| How can I tell if things are going well?

In OL check properties of your pst, that will show whether its unicode.
If not, within OL FileNewData File that will create a new unicode pst.
If required copy data from old pst to this new one. Set new as the default
mail store.
In OE export msgs - I dont know how identities are treated but I suspect
only the current Identity store would be exported

"Richard Eich" wrote in message
.. .
wrote...
Remember, you must be using a unicode .pst file in Outlook 2003 to
import anything over 1.87 gigs of information. Otherwise, Outlook will
hurl.

Funny you mention that -- that's exactly what happened.

Two questions, to which a URL or the right search words will help me
STFW:

1) How do I establish a unicode *.pst prior to import?

2) I have multiple OE identities. Does OL 2003 support that?

Thanks very much.


--?
Milly Staples [MVP - Outlook]

Post all replies to the group to keep the discussion intact. All
unsolicited mail sent to my personal account will be deleted without
reading.

After furious head scratching, Richard Eich asked:

| address@invalid wrote...
|| Ideally you should export from OE to OL.
|| Not knowing much about OE I'd have thought your inbox.dbx was overly
|| large for correct operation of OE
|
| With me readily assuming all the risk here, how much harm could I do
| to kill OL, kill msimn.exe if need be, and try to export from OE
| rather than import?
|
| (Yes, the file sizes have been a little problematic.)
|
|| "Richard Eich" wrote in message
||| XP Pro SP2, w/auto updates enabled
|||
||| I'm trying to import messages from OE6 into Office 2003 Outlook,
||| after up upgrade to both IE7 (from IE6) and Office 2003 (from Office
||| 2000, without Outlook installed).
|||
||| The .dbx files are very large (e.g., inbox.dbx, nearly 1GB) and
||| there are a lot of them.
|||
||| Outlook has been hour-glassed for almost 9 hours. msimn.exe has
||| been as high as 28MB, although it's around 13MB now.
|||
||| How can I tell if things are going well?

DL address@invalid wrote:

In OE export msgs - I dont know how identities are treated but I
suspect only the current Identity store would be exported

DL is correct here. In order to port the data from multiple identities, you
must export the first identity's data, then make the next identity the
default, export its data, and so on, until all identities are exported. If
you wish to keep them separate in Outlook (i.e., in different folders or
PSTs, you'll either have to move messages manually to other PSTs/folders in
Outlook after each OE export or use separate mail profiles (and PSTs) for
each identity.
--
Brian Tillman

address@invalid wrote...
In OL check properties of your pst, that will show whether its unicode.

File Data File Management [outlook.pst] Open Folder Props

....says outlook.pst is an Outlook Data File. Nothing about unicode.

If not, within OL FileNewData File that will create a new unicode pst.
If required copy data from old pst to this new one. Set new as the default
mail store.

I've got some reading to do. Thanks for your help.

In OE export msgs - I dont know how identities are treated but I suspect
only the current Identity store would be exported

"Richard Eich" wrote in message
.. .
wrote...
Remember, you must be using a unicode .pst file in Outlook 2003 to
import anything over 1.87 gigs of information. Otherwise, Outlook will
hurl.

Funny you mention that -- that's exactly what happened.

Two questions, to which a URL or the right search words will help me
STFW:

1) How do I establish a unicode *.pst prior to import?

2) I have multiple OE identities. Does OL 2003 support that?

Thanks very much.


--?
Milly Staples [MVP - Outlook]

Post all replies to the group to keep the discussion intact. All
unsolicited mail sent to my personal account will be deleted without
reading.

After furious head scratching, Richard Eich asked:

| address@invalid wrote...
|| Ideally you should export from OE to OL.
|| Not knowing much about OE I'd have thought your inbox.dbx was overly
|| large for correct operation of OE
|
| With me readily assuming all the risk here, how much harm could I do
| to kill OL, kill msimn.exe if need be, and try to export from OE
| rather than import?
|
| (Yes, the file sizes have been a little problematic.)
|
|| "Richard Eich" wrote in message
||| XP Pro SP2, w/auto updates enabled
|||
||| I'm trying to import messages from OE6 into Office 2003 Outlook,
||| after up upgrade to both IE7 (from IE6) and Office 2003 (from Office
||| 2000, without Outlook installed).
|||
||| The .dbx files are very large (e.g., inbox.dbx, nearly 1GB) and
||| there are a lot of them.
|||
||| Outlook has been hour-glassed for almost 9 hours. msimn.exe has
||| been as high as 28MB, although it's around 13MB now.
|||
||| How can I tell if things are going well?

Properties of pst (unicode) woops! my error

"Richard Eich" wrote in message
.. .
address@invalid wrote...
In OL check properties of your pst, that will show whether its unicode.

File Data File Management [outlook.pst] Open Folder Props

...says outlook.pst is an Outlook Data File. Nothing about unicode.

If not, within OL FileNewData File that will create a new unicode
pst.
If required copy data from old pst to this new one. Set new as the
default
mail store.

I've got some reading to do. Thanks for your help.

In OE export msgs - I dont know how identities are treated but I suspect
only the current Identity store would be exported

"Richard Eich" wrote in message
.. .
wrote...
Remember, you must be using a unicode .pst file in Outlook 2003 to
import anything over 1.87 gigs of information. Otherwise, Outlook will
hurl.

Funny you mention that -- that's exactly what happened.

Two questions, to which a URL or the right search words will help me
STFW:

1) How do I establish a unicode *.pst prior to import?

2) I have multiple OE identities. Does OL 2003 support that?

Thanks very much.


--?
Milly Staples [MVP - Outlook]

Post all replies to the group to keep the discussion intact. All
unsolicited mail sent to my personal account will be deleted without
reading.

After furious head scratching, Richard Eich asked:

| address@invalid wrote...
|| Ideally you should export from OE to OL.
|| Not knowing much about OE I'd have thought your inbox.dbx was
overly
|| large for correct operation of OE
|
| With me readily assuming all the risk here, how much harm could I
do
| to kill OL, kill msimn.exe if need be, and try to export from OE
| rather than import?
|
| (Yes, the file sizes have been a little problematic.)
|
|| "Richard Eich" wrote in message
||| XP Pro SP2, w/auto updates enabled
|||
||| I'm trying to import messages from OE6 into Office 2003 Outlook,
||| after up upgrade to both IE7 (from IE6) and Office 2003 (from
Office
||| 2000, without Outlook installed).
|||
||| The .dbx files are very large (e.g., inbox.dbx, nearly 1GB) and
||| there are a lot of them.
|||
||| Outlook has been hour-glassed for almost 9 hours. msimn.exe has
||| been as high as 28MB, although it's around 13MB now.
|||
||| How can I tell if things are going well?

Richard Eich wrote:

address@invalid wrote...
In OL check properties of your pst, that will show whether its
unicode.

File Data File Management [outlook.pst] Open Folder Props

...says outlook.pst is an Outlook Data File. Nothing about unicode.

It will contain the string "97-2002" if it is an ANSI (older) format PST and
it will not contain that string if it is Unicode.

I've got some reading to do. Thanks for your help.

Google Groups should find the other times that the process has been
described in the Outlook newsgroups. I have posted it personally at least
four times.
--
Brian Tillman