Front Page 2003 Open File problem

[Charles Barnum]

Okay, I'll give you a million bucks if you can solve this problem.
I build Excel databases for genealogy. I used to be able to save them as
Formatted Text using the save-as command.
Then I'd open them in Front Page 2003 and they would appear exactly as they
did in Excel. In code view in FP2003, the tags of <Pre></pre> would be added
automatically.
Now the added files appear as a jumbled mess with no tages, etc.
This started with Excel 2007. But when I try it will an older Formatted Text
file I created before I bought Excel 2007, they still work just fine.
Therefore, I concude that Excel 2007 has messed up the way it Saves-as
Formatted Text files (prn files).
Can anyone solve this problem or is this a bug in Excel 2007 that will never
be fixed because they are not intereted in a problem that affects only a few
thousand genealogists?
Remember I have the million bucks waiting.

 

[Stefan B Rusynko]

Have you asked about the change in an Excel newsgroup?

Although not recommended (Access is the preferred way to handle a datasource) you can use Excel as datasource
See http://support.microsoft.com/default.aspx?scid=268948

--

_____________________________________________
SBR @ ENJOY (-: [ Microsoft MVP - FrontPage ]
"Warning - Using the F1 Key will not break anything!" (-;
_____________________________________________


| Okay, I'll give you a million bucks if you can solve this problem.
| I build Excel databases for genealogy. I used to be able to save them as
| Formatted Text using the save-as command.
| Then I'd open them in Front Page 2003 and they would appear exactly as they
| did in Excel. In code view in FP2003, the tags of <Pre></pre> would be added
| automatically.
| Now the added files appear as a jumbled mess with no tages, etc.
| This started with Excel 2007. But when I try it will an older Formatted Text
| file I created before I bought Excel 2007, they still work just fine.
| Therefore, I concude that Excel 2007 has messed up the way it Saves-as
| Formatted Text files (prn files).
| Can anyone solve this problem or is this a bug in Excel 2007 that will never
| be fixed because they are not intereted in a problem that affects only a few
| thousand genealogists?
| Remember I have the million bucks waiting.
| --
| Charles
| --
| Charles

 

[Charles Barnum]

Let me say this one more time after saying it to people all over America.
I used to be able to SAVE-AS an Excel file as Formatted Text. (That's a prn
file.)
I'd then INSERT that file in FP2003. FP2003 would format the INSERTED file
with <pre> </pre> tags automatically. Since MS came out with Excel 2007, I
can no longer do that. All I get is a jumbled mess of data on the View
section of FP2003. Now to insert an Excel file with <pre> tags I have to do
it manually. I have to open the prn file from Excel in WordPad, copy it, go
to Code view in FP2003, create the <pre> html tags and manually insert the
file. Then switch to View page.
This is a waste of time. No one at MS seems to know or care why or how they
changed the way Excel creates Formatte text (prn files) making them
incompatable with FP2003.
I donot care to do the insert task any other way. It was just wonderful
before Excel 2007 came out. Now it' tedious. Genealogists all over America
who bought Excel 2007 have to go thru the same time-consuming process that
used to take 30 seconds.
About a month before Excel 2007 came out, MS had an update for all Excel
versions. It also changed the way the older versions handled Formatted Text
files. Whatever they did to screw it up, I hope they will unscrew it.
--
Charles

Have you asked about the change in an Excel newsgroup?

Although not recommended (Access is the preferred way to handle a datasource) you can use Excel as datasource
See http://support.microsoft.com/default.aspx?scid=268948

--

_____________________________________________
SBR @ ENJOY (-: [ Microsoft MVP - FrontPage ]
"Warning - Using the F1 Key will not break anything!" (-;
_____________________________________________


| Okay, I'll give you a million bucks if you can solve this problem.
| I build Excel databases for genealogy. I used to be able to save them as
| Formatted Text using the save-as command.
| Then I'd open them in Front Page 2003 and they would appear exactly as they
| did in Excel. In code view in FP2003, the tags of <Pre></pre> would be added
| automatically.
| Now the added files appear as a jumbled mess with no tages, etc.
| This started with Excel 2007. But when I try it will an older Formatted Text
| file I created before I bought Excel 2007, they still work just fine.
| Therefore, I concude that Excel 2007 has messed up the way it Saves-as
| Formatted Text files (prn files).
| Can anyone solve this problem or is this a bug in Excel 2007 that will never
| be fixed because they are not intereted in a problem that affects only a few
| thousand genealogists?
| Remember I have the million bucks waiting.
| --
| Charles

 

[Thomas A. Rowe]

You need to post this to the Excel newsgroup, as this is not a FP issue as far how to save data from
Excel.

--
==============================================
Thomas A. Rowe
Microsoft MVP - FrontPage

http://www.Ecom-Data.com
==============================================

Let me say this one more time after saying it to people all over America.
I used to be able to SAVE-AS an Excel file as Formatted Text. (That's a prn
file.)
I'd then INSERT that file in FP2003. FP2003 would format the INSERTED file
with <pre> </pre> tags automatically. Since MS came out with Excel 2007, I
can no longer do that. All I get is a jumbled mess of data on the View
section of FP2003. Now to insert an Excel file with <pre> tags I have to do
it manually. I have to open the prn file from Excel in WordPad, copy it, go
to Code view in FP2003, create the <pre> html tags and manually insert the
file. Then switch to View page.
This is a waste of time. No one at MS seems to know or care why or how they
changed the way Excel creates Formatte text (prn files) making them
incompatable with FP2003.
I donot care to do the insert task any other way. It was just wonderful
before Excel 2007 came out. Now it' tedious. Genealogists all over America
who bought Excel 2007 have to go thru the same time-consuming process that
used to take 30 seconds.
About a month before Excel 2007 came out, MS had an update for all Excel
versions. It also changed the way the older versions handled Formatted Text
files. Whatever they did to screw it up, I hope they will unscrew it.
--
Charles

Have you asked about the change in an Excel newsgroup?

Although not recommended (Access is the preferred way to handle a datasource) you can use Excel
as datasource
See http://support.microsoft.com/default.aspx?scid=268948

--

_____________________________________________
SBR @ ENJOY (-: [ Microsoft MVP - FrontPage ]
"Warning - Using the F1 Key will not break anything!" (-;
_____________________________________________


| Okay, I'll give you a million bucks if you can solve this problem.
| I build Excel databases for genealogy. I used to be able to save them as
| Formatted Text using the save-as command.
| Then I'd open them in Front Page 2003 and they would appear exactly as they
| did in Excel. In code view in FP2003, the tags of <Pre></pre> would be added
| automatically.
| Now the added files appear as a jumbled mess with no tages, etc.
| This started with Excel 2007. But when I try it will an older Formatted Text
| file I created before I bought Excel 2007, they still work just fine.
| Therefore, I concude that Excel 2007 has messed up the way it Saves-as
| Formatted Text files (prn files).
| Can anyone solve this problem or is this a bug in Excel 2007 that will never
| be fixed because they are not intereted in a problem that affects only a few
| thousand genealogists?
| Remember I have the million bucks waiting.
| --
| Charles

 

[Charles Barnum]

Howdy,
I did post to the Excel group. No answer.
This is a FP 2003 issue too. It's all MS, ya' know.
Instead of answering my question I get a game of hide and seek.
Charles

You need to post this to the Excel newsgroup, as this is not a FP issue as far how to save data from
Excel.

--
==============================================
Thomas A. Rowe
Microsoft MVP - FrontPage

http://www.Ecom-Data.com
==============================================

Let me say this one more time after saying it to people all over America.
I used to be able to SAVE-AS an Excel file as Formatted Text. (That's a prn
file.)
I'd then INSERT that file in FP2003. FP2003 would format the INSERTED file
with <pre> </pre> tags automatically. Since MS came out with Excel 2007, I
can no longer do that. All I get is a jumbled mess of data on the View
section of FP2003. Now to insert an Excel file with <pre> tags I have to do
it manually. I have to open the prn file from Excel in WordPad, copy it, go
to Code view in FP2003, create the <pre> html tags and manually insert the
file. Then switch to View page.
This is a waste of time. No one at MS seems to know or care why or how they
changed the way Excel creates Formatte text (prn files) making them
incompatable with FP2003.
I donot care to do the insert task any other way. It was just wonderful
before Excel 2007 came out. Now it' tedious. Genealogists all over America
who bought Excel 2007 have to go thru the same time-consuming process that
used to take 30 seconds.
About a month before Excel 2007 came out, MS had an update for all Excel
versions. It also changed the way the older versions handled Formatted Text
files. Whatever they did to screw it up, I hope they will unscrew it.
--
Charles

Have you asked about the change in an Excel newsgroup?

Although not recommended (Access is the preferred way to handle a datasource) you can use Excel
as datasource
See http://support.microsoft.com/default.aspx?scid=268948

--

_____________________________________________
SBR @ ENJOY (-: [ Microsoft MVP - FrontPage ]
"Warning - Using the F1 Key will not break anything!" (-;
_____________________________________________


| Okay, I'll give you a million bucks if you can solve this problem.
| I build Excel databases for genealogy. I used to be able to save them as
| Formatted Text using the save-as command.
| Then I'd open them in Front Page 2003 and they would appear exactly as they
| did in Excel. In code view in FP2003, the tags of <Pre></pre> would be added
| automatically.
| Now the added files appear as a jumbled mess with no tages, etc.
| This started with Excel 2007. But when I try it will an older Formatted Text
| file I created before I bought Excel 2007, they still work just fine.
| Therefore, I concude that Excel 2007 has messed up the way it Saves-as
| Formatted Text files (prn files).
| Can anyone solve this problem or is this a bug in Excel 2007 that will never
| be fixed because they are not intereted in a problem that affects only a few
| thousand genealogists?
| Remember I have the million bucks waiting.
| --
| Charles

 

[Thomas A. Rowe]

How is this a FP issue?

FP was released prior to Excel 2007, and as you indicated, it had work in the past with prior
version of Excel.

--
==============================================
Thomas A. Rowe
Microsoft MVP - FrontPage

http://www.Ecom-Data.com
==============================================

Howdy,
I did post to the Excel group. No answer.
This is a FP 2003 issue too. It's all MS, ya' know.
Instead of answering my question I get a game of hide and seek.
Charles

You need to post this to the Excel newsgroup, as this is not a FP issue as far how to save data
from
Excel.

--
==============================================
Thomas A. Rowe
Microsoft MVP - FrontPage

http://www.Ecom-Data.com
==============================================

Let me say this one more time after saying it to people all over America.
I used to be able to SAVE-AS an Excel file as Formatted Text. (That's a prn
file.)
I'd then INSERT that file in FP2003. FP2003 would format the INSERTED file
with <pre> </pre> tags automatically. Since MS came out with Excel 2007, I
can no longer do that. All I get is a jumbled mess of data on the View
section of FP2003. Now to insert an Excel file with <pre> tags I have to do
it manually. I have to open the prn file from Excel in WordPad, copy it, go
to Code view in FP2003, create the <pre> html tags and manually insert the
file. Then switch to View page.
This is a waste of time. No one at MS seems to know or care why or how they
changed the way Excel creates Formatte text (prn files) making them
incompatable with FP2003.
I donot care to do the insert task any other way. It was just wonderful
before Excel 2007 came out. Now it' tedious. Genealogists all over America
who bought Excel 2007 have to go thru the same time-consuming process that
used to take 30 seconds.
About a month before Excel 2007 came out, MS had an update for all Excel
versions. It also changed the way the older versions handled Formatted Text
files. Whatever they did to screw it up, I hope they will unscrew it.
--
Charles


:

Have you asked about the change in an Excel newsgroup?

Although not recommended (Access is the preferred way to handle a datasource) you can use
Excel
as datasource
See http://support.microsoft.com/default.aspx?scid=268948

--

_____________________________________________
SBR @ ENJOY (-: [ Microsoft MVP - FrontPage ]
"Warning - Using the F1 Key will not break anything!" (-;
_____________________________________________


| Okay, I'll give you a million bucks if you can solve this problem.
| I build Excel databases for genealogy. I used to be able to save them as
| Formatted Text using the save-as command.
| Then I'd open them in Front Page 2003 and they would appear exactly as they
| did in Excel. In code view in FP2003, the tags of <Pre></pre> would be added
| automatically.
| Now the added files appear as a jumbled mess with no tages, etc.
| This started with Excel 2007. But when I try it will an older Formatted Text
| file I created before I bought Excel 2007, they still work just fine.
| Therefore, I concude that Excel 2007 has messed up the way it Saves-as
| Formatted Text files (prn files).
| Can anyone solve this problem or is this a bug in Excel 2007 that will never
| be fixed because they are not intereted in a problem that affects only a few
| thousand genealogists?
| Remember I have the million bucks waiting.
| --
| Charles

 

[Bob Lehmann]

It's all MS, ya' know.

hmmmmmmmmmm......

Well maybe you should post it to an Age of Empires group then.

Bob Lehmann

Howdy,
I did post to the Excel group. No answer.
This is a FP 2003 issue too. It's all MS, ya' know.
Instead of answering my question I get a game of hide and seek.
Charles

You need to post this to the Excel newsgroup, as this is not a FP issue as far how to save data from
Excel.

--
==============================================
Thomas A. Rowe
Microsoft MVP - FrontPage

http://www.Ecom-Data.com
==============================================

Let me say this one more time after saying it to people all over America.
I used to be able to SAVE-AS an Excel file as Formatted Text. (That's a prn
file.)
I'd then INSERT that file in FP2003. FP2003 would format the INSERTED file
with <pre> </pre> tags automatically. Since MS came out with Excel 2007, I
can no longer do that. All I get is a jumbled mess of data on the View
section of FP2003. Now to insert an Excel file with <pre> tags I have to do
it manually. I have to open the prn file from Excel in WordPad, copy it, go
to Code view in FP2003, create the <pre> html tags and manually insert the
file. Then switch to View page.
This is a waste of time. No one at MS seems to know or care why or how they
changed the way Excel creates Formatte text (prn files) making them
incompatable with FP2003.
I donot care to do the insert task any other way. It was just wonderful
before Excel 2007 came out. Now it' tedious. Genealogists all over America
who bought Excel 2007 have to go thru the same time-consuming process that
used to take 30 seconds.
About a month before Excel 2007 came out, MS had an update for all Excel
versions. It also changed the way the older versions handled Formatted Text
files. Whatever they did to screw it up, I hope they will unscrew it.
--
Charles


:

Have you asked about the change in an Excel newsgroup?

Although not recommended (Access is the preferred way to handle a datasource) you can use Excel
as datasource
See http://support.microsoft.com/default.aspx?scid=268948

--

_____________________________________________
SBR @ ENJOY (-: [ Microsoft MVP - FrontPage ]
"Warning - Using the F1 Key will not break anything!" (-;
_____________________________________________


| Okay, I'll give you a million bucks if you can solve this problem.
| I build Excel databases for genealogy. I used to be able to save them as
| Formatted Text using the save-as command.
| Then I'd open them in Front Page 2003 and they would appear exactly as they
| did in Excel. In code view in FP2003, the tags of <Pre></pre> would be added
| automatically.
| Now the added files appear as a jumbled mess with no tages, etc.
| This started with Excel 2007. But when I try it will an older Formatted Text
| file I created before I bought Excel 2007, they still work just fine.
| Therefore, I concude that Excel 2007 has messed up the way it Saves-as
| Formatted Text files (prn files).
| Can anyone solve this problem or is this a bug in Excel 2007 that will never
| be fixed because they are not intereted in a problem that affects only a few
| thousand genealogists?
| Remember I have the million bucks waiting.
| --
| Charles

 

[Charles Barnum]

If you do not have any answers, please do not respond to my post. I need
answers not stupid insults. Otherwise, this forum is a waste of time.
Charles
--

hmmmmmmmmmm......

Well maybe you should post it to an Age of Empires group then.

Bob Lehmann

Howdy,
I did post to the Excel group. No answer.
This is a FP 2003 issue too. It's all MS, ya' know.
Instead of answering my question I get a game of hide and seek.
Charles

You need to post this to the Excel newsgroup, as this is not a FP issue as far how to save data from
Excel.

--
==============================================
Thomas A. Rowe
Microsoft MVP - FrontPage

http://www.Ecom-Data.com
==============================================


Let me say this one more time after saying it to people all over America.
I used to be able to SAVE-AS an Excel file as Formatted Text. (That's a prn
file.)
I'd then INSERT that file in FP2003. FP2003 would format the INSERTED file
with <pre> </pre> tags automatically. Since MS came out with Excel 2007, I
can no longer do that. All I get is a jumbled mess of data on the View
section of FP2003. Now to insert an Excel file with <pre> tags I have to do
it manually. I have to open the prn file from Excel in WordPad, copy it, go
to Code view in FP2003, create the <pre> html tags and manually insert the
file. Then switch to View page.
This is a waste of time. No one at MS seems to know or care why or how they
changed the way Excel creates Formatte text (prn files) making them
incompatable with FP2003.
I donot care to do the insert task any other way. It was just wonderful
before Excel 2007 came out. Now it' tedious. Genealogists all over America
who bought Excel 2007 have to go thru the same time-consuming process that
used to take 30 seconds.
About a month before Excel 2007 came out, MS had an update for all Excel
versions. It also changed the way the older versions handled Formatted Text
files. Whatever they did to screw it up, I hope they will unscrew it.
--
Charles


:

Have you asked about the change in an Excel newsgroup?

Although not recommended (Access is the preferred way to handle a datasource) you can use Excel
as datasource
See http://support.microsoft.com/default.aspx?scid=268948

--

_____________________________________________
SBR @ ENJOY (-: [ Microsoft MVP - FrontPage ]
"Warning - Using the F1 Key will not break anything!" (-;
_____________________________________________


| Okay, I'll give you a million bucks if you can solve this problem.
| I build Excel databases for genealogy. I used to be able to save them as
| Formatted Text using the save-as command.
| Then I'd open them in Front Page 2003 and they would appear exactly as they
| did in Excel. In code view in FP2003, the tags of <Pre></pre> would be added
| automatically.
| Now the added files appear as a jumbled mess with no tages, etc.
| This started with Excel 2007. But when I try it will an older Formatted Text
| file I created before I bought Excel 2007, they still work just fine.
| Therefore, I concude that Excel 2007 has messed up the way it Saves-as
| Formatted Text files (prn files).
| Can anyone solve this problem or is this a bug in Excel 2007 that will never
| be fixed because they are not intereted in a problem that affects only a few
| thousand genealogists?
| Remember I have the million bucks waiting.
| --
| Charles

 

[Ronx]

A Formatted Text File (.prn) is not a web page. It is a flat text file
suitable for putting through a common dot matrix printer with no printer
drivers. It is "formatted" by the addition of spaces to maintain the
columns.

The web page Excel 2007 can output is a choice of .htm pages or .mht
pages. Just for a change, the HTM page output is pretty clean with
external style sheet. It is a table, with no <pre> tags.

 

[Stefan B Rusynko]

Or it should be saved as a .csv (not a .prn)
Text (Tab Delimited) file

Space delimited files should never be uses as data source
(spaces in the field values will break the results)
--

_____________________________________________
SBR @ ENJOY (-: [ Microsoft MVP - FrontPage ]
"Warning - Using the F1 Key will not break anything!" (-;
_____________________________________________


|A Formatted Text File (.prn) is not a web page. It is a flat text file
| suitable for putting through a common dot matrix printer with no printer
| drivers. It is "formatted" by the addition of spaces to maintain the
| columns.
|
| The web page Excel 2007 can output is a choice of .htm pages or .mht
| pages. Just for a change, the HTM page output is pretty clean with
| external style sheet. It is a table, with no <pre> tags.
| --
| Ron Symonds - Microsoft MVP (FrontPage)
| Reply only to group - emails will be deleted unread.
| FrontPage Support: http://www.frontpagemvps.com/
| http://www.rxs-enterprises.org/fp
|
|
|
| |
| > Okay, I'll give you a million bucks if you can solve this problem.
| > I build Excel databases for genealogy. I used to be able to save them as
| > Formatted Text using the save-as command.
| > Then I'd open them in Front Page 2003 and they would appear exactly as they
| > did in Excel. In code view in FP2003, the tags of <Pre></pre> would be added
| > automatically.
| > Now the added files appear as a jumbled mess with no tages, etc.
| > This started with Excel 2007. But when I try it will an older Formatted Text
| > file I created before I bought Excel 2007, they still work just fine.
| > Therefore, I concude that Excel 2007 has messed up the way it Saves-as
| > Formatted Text files (prn files).
| > Can anyone solve this problem or is this a bug in Excel 2007 that will never
| > be fixed because they are not intereted in a problem that affects only a few
| > thousand genealogists?
| > Remember I have the million bucks waiting.
| > --
| > Charles
| > --
| > Charles
|

 

[Charles Barnum]

I know that the Formatted Text files generated by Excel are not web pages.
I've been doing this for work since 1988. I've put over 2 million datum
entries online. I would never use an Excel work sheet in my website because
the html code it generates is massive.
Prior to the changes made in Excel, I used to be able to open a a page in FP
, click "Insert," then Click "File" select a prn file generated by Excel. A
CONVERT BOX would open in FP with the following choices:
One formatted paragraph,
Formatted Paragraphs,
Normal paragraphs,
Normal paragraphs with line breaks,
and finally-
Do Not Convert.
I'd select Formatted paragraphs and click OK.
The File would appear automatically in Design View.
In the Code View the large file would begin with <pre> and end with </pre>
tags.
No other html code would appear saving a huge amount of web space and load
time for patrons.
However, now that Excel has somehow changed how they save those Formatted
Text files, NONE of them will automatically open in FP. They appear as a
jumbled mess. However, I can go back to a file created using the an older
Excel program and it works perfectly well in FP.
Something has changed. Is it a FP Problem? Is it an Excel problem? I only
know that the two programs no longer are compatible in that specific
instance. The reason I buy only MS products is I want everything to work
together. Yes, I can get around the problem by using WordPad and setting up
the <pre> tags myself, but FP was designed to CONVERT formatted text files
made by Excel, but it is NO longer is capable of doing so. There is a
problem. I'm a genealogist, nor a software techie. I'm not the only
genealogist who has noticed this new problem. No one has an answer to Fix it.
Since FP and Excel ar the two most used tools in genealogy today, I hope
someone at MS becomes aware of this problem and corrects it with an update
fix. If it is not fixed, there is little need for genealogists to buy Excel
anymore. One of the free spreadsheet programs will work just as well. I'll be
placing this post on a genealogy forum today. I hope I can report back to
them at a later time that MS is serious about fixing their products.

--
Charles

A Formatted Text File (.prn) is not a web page. It is a flat text file
suitable for putting through a common dot matrix printer with no printer
drivers. It is "formatted" by the addition of spaces to maintain the
columns.

The web page Excel 2007 can output is a choice of .htm pages or .mht
pages. Just for a change, the HTM page output is pretty clean with
external style sheet. It is a table, with no <pre> tags.
--
Ron Symonds - Microsoft MVP (FrontPage)
Reply only to group - emails will be deleted unread.
FrontPage Support: http://www.frontpagemvps.com/
http://www.rxs-enterprises.org/fp

 

[Ronx]

Something has changed. Is it a FP Problem? Is it an Excel problem?

FrontPage has not changed, so it must be Excel - the HTML output from
Excel 2007 (Save as HTML file) has definitely changed: there is now very
little bloat, and the output is tabular which normally suits data from a
spreadsheet.

Since Excel has changed, I suggest you ask in an Excel group.
--
Ron Symonds - Microsoft MVP (FrontPage)
Reply only to group - emails will be deleted unread.
FrontPage Support: http://www.frontpagemvps.com/
http://www.rxs-enterprises.org/fp

I know that the Formatted Text files generated by Excel are not web pages.
I've been doing this for work since 1988. I've put over 2 million datum
entries online. I would never use an Excel work sheet in my website because
the html code it generates is massive.
Prior to the changes made in Excel, I used to be able to open a a page in FP
, click "Insert," then Click "File" select a prn file generated by Excel. A
CONVERT BOX would open in FP with the following choices:
One formatted paragraph,
Formatted Paragraphs,
Normal paragraphs,
Normal paragraphs with line breaks,
and finally-
Do Not Convert.
I'd select Formatted paragraphs and click OK.
The File would appear automatically in Design View.
In the Code View the large file would begin with <pre> and end with </pre>
tags.
No other html code would appear saving a huge amount of web space and load
time for patrons.
However, now that Excel has somehow changed how they save those Formatted
Text files, NONE of them will automatically open in FP. They appear as a
jumbled mess. However, I can go back to a file created using the an older
Excel program and it works perfectly well in FP.
Something has changed. Is it a FP Problem? Is it an Excel problem? I only
know that the two programs no longer are compatible in that specific
instance. The reason I buy only MS products is I want everything to work
together. Yes, I can get around the problem by using WordPad and setting up
the <pre> tags myself, but FP was designed to CONVERT formatted text files
made by Excel, but it is NO longer is capable of doing so. There is a
problem. I'm a genealogist, nor a software techie. I'm not the only
genealogist who has noticed this new problem. No one has an answer to Fix it.
Since FP and Excel ar the two most used tools in genealogy today, I hope
someone at MS becomes aware of this problem and corrects it with an update
fix. If it is not fixed, there is little need for genealogists to buy Excel
anymore. One of the free spreadsheet programs will work just as well. I'll be
placing this post on a genealogy forum today. I hope I can report back to
them at a later time that MS is serious about fixing their products.

 

[Bob Lehmann]

I suggest you ask in an Excel group.

Or Age of Empires, since that is also a Microsoft group, and is probably
also not compatible with the new version of Excel.

Bob Lehmann