KB943985

K

kspexet

I submitted the following information to Microsoft but have not heard
anything about a fix for this. Has anyone else seen this issue and have you
been able to resolve it?

CUSTOMER PROVIDED SYSTEM PROPERTIES
O/S: Windows XP SP2
Br: IE 6 SP2
Country/Region: United States

CONTACT INFORMATION
First Name: Kathy
Last Name: Spexet

PRODUCT
Office Professional Edition 2003

QUESTIONS OR COMMENTS
Message: Our users are reporting the following issue after the KB943985
update:
The last round of Microsoft Office patches pushed out has changed how Excel
opens text files. If you either do a "right click open as" (i.e. right click
in explorer on the txt file to open) or execute excel with a command line
(excel.exe filename.txt) it is automatically running the Text to ! Columns
(Text Import Wizard) and parsing the data as if it is the default fixed
width. It usually makes the wrong choices to parse the data. This is the
same behavior that CSV files had before the patch was pushed out.

Before the patch, doing a "right click open as" on a text file or a command
line execution of excel would just open the text file with all of the data in
the first column. At that point the users could then highlight the first
column and then do a Data, Text to Columns to parse the data as needed.
Doing a File, Open will open the text file in the first column and
automatically start the Text Import Wizard (Text to Columns) interactively.

Our users do not think that Excel should automatically parse text files … it
should allow the user run the Text Import Wizard interactively. The only
workaround have for the users right now is to close the badly parsed file
without saving and then do a File, Open and try again.

I am hoping that you can find us a solution to get our functionality back
for text files. A registry hack would be fine.
 
B

Bob Buckland ?:-\)

Hi Kathy,

The security update was re-released in May. You may also want to look over the related knowledge base article.
http://support.microsoft.com/kb/943985?FR=1
At the bottom of the article in is a link to a hotfix (952208) that may help.

You may want to also review the issues addressed though in the Security Bulletin
http://microsoft.com/technet/security/bulleting/ms08-014.mspx
for Excel for additional details on why some of the changes were made, which include additional file data validation on import.

=================
I submitted the following information to Microsoft but have not heard
anything about a fix for this. Has anyone else seen this issue and have you
been able to resolve it?

CUSTOMER PROVIDED SYSTEM PROPERTIES
O/S: Windows XP SP2
Br: IE 6 SP2
Country/Region: United States

CONTACT INFORMATION
First Name: Kathy
Last Name: Spexet

PRODUCT
Office Professional Edition 2003

QUESTIONS OR COMMENTS
Message: Our users are reporting the following issue after the KB943985
update:
The last round of Microsoft Office patches pushed out has changed how Excel
opens text files. If you either do a "right click open as" (i.e. right click
in explorer on the txt file to open) or execute excel with a command line
(excel.exe filename.txt) it is automatically running the Text to ! Columns
(Text Import Wizard) and parsing the data as if it is the default fixed
width. It usually makes the wrong choices to parse the data. This is the
same behavior that CSV files had before the patch was pushed out.

Before the patch, doing a "right click open as" on a text file or a command
line execution of excel would just open the text file with all of the data in
the first column. At that point the users could then highlight the first
column and then do a Data, Text to Columns to parse the data as needed.
Doing a File, Open will open the text file in the first column and
automatically start the Text Import Wizard (Text to Columns) interactively.

Our users do not think that Excel should automatically parse text files . it
should allow the user run the Text Import Wizard interactively. The only
workaround have for the users right now is to close the badly parsed file
without saving and then do a File, Open and try again.

I am hoping that you can find us a solution to get our functionality back
for text files. A registry hack would be fine. >>
--

Bob Buckland ?:)
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*
 
B

Bob Buckland ?:-\)

Hi Kathy,

Yes, that's the hotfix I mentioned previously :)

==========
Bob,
I know this fix was reissued in May. That is the one that we already have
installed.

I actually found the information I needed in the forum. There is a hotfix
available for this that was issued on May 10th.

http://support.microsoft.com/kb/952208

Kathy >>
--

Bob Buckland ?:)
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top