FP Inserting Huge Chunks of Blank Lines

[msnews.microsoft.com]

I've encountered a problem that I have been unable to resolve- I haven't
seen it addressed anywhere.

I've got two pages used for home pages for a web site - one is for high res
users and the other is for low res - other than the table layouts and sizes,
everything on each page is identical.

When I modify one of them, however, FP2K3 inserts literally thousands of
lines of blank space - so much so that the file size increases from around
35KB up to 750KB or so. It has never modified the other page at all.

I can delete all the lines, but two or three days later, when I modify the
page again, it does the same thing.

Any ideas?

Thanks!

 

[Stefan B Rusynko]

Somehow the page is corrupt
- delete it and make a copy if the other good one to edit

--




| I've encountered a problem that I have been unable to resolve- I haven't
| seen it addressed anywhere.
|
| I've got two pages used for home pages for a web site - one is for high res
| users and the other is for low res - other than the table layouts and sizes,
| everything on each page is identical.
|
| When I modify one of them, however, FP2K3 inserts literally thousands of
| lines of blank space - so much so that the file size increases from around
| 35KB up to 750KB or so. It has never modified the other page at all.
|
| I can delete all the lines, but two or three days later, when I modify the
| page again, it does the same thing.
|
| Any ideas?
|
| Thanks!
|
|

 

[Ronx]

How does your site react to the many users with high-res screens and
small (800x600) browser windows? Or users with the sidebars opened
wide in the browser?
IMO designing separate pages for different screen resolutions is often
a waste of effort (but your mileage may vary).

 

[msnews.microsoft.com]

I agree, but the dude who paid me to build the site wanted a page that
didn't scroll off the screen, and with the content in the middle of the
page, it was impossible to build a page that would expand without hosing up
the format. So we bilt the large one for the 75% of the folks using it, and
the small one. The index page has a script that determines which resolution
the viewer uses and automatically redirects to the correct page! It works
fine from a technical standpoint.

Thanks for the assist! We'll recreate the page and see if that works.

I don't suppose anyone know *how* it corrupted - what caused it to get that
way?