I've searched the forums and couldn't find this addressed...

It seems that I've been able to get sliding up to work correctly for everything except text objects (field labels). As long as the text objects are on one page (don't cross a page break), they will slide up correctly. As soon as they are moved below the first page break, they just disappear in Preview / Print. The other objects (fields, rectangles, lines, etc.) slide up fine, but the text objects are gone.

I've attached a simple file to show this working. I'd appreciate it if someone could confirm that this works or doen't work for them as well. It smells like a bug.

Of course, I could make the field labels fields themselves with either global data or a simple calculation, but I have a hard time keeping the few fields and globals I currently have straight and would like to find a "proper" solution for this.

I'm on FMP7 and MacOS X.

Thanks.

Chris

test.fp7.zip

Chris, I can confirm your problem: FileMaker Pro 7.0v1 on Mac OS 10.3.3.

Text object (field label or mergefields) do not show up in previewmode and do not print, when they are below the first pagebreak on a multi-page-layout, when they are told to slide up.

They do slide to the first page to print, but they don't show up.

They do however show and print correctly when they are on the second page to print.

Font or size makes no difference.

I can not find a confirmation of this bug on the Tech Info-section of FileMaker, nor have I been able to find more information about this behaviour.

In fact: you are the only person I see that is having the same trouble, and I see that your problem is already 3 weeks old.

Can anyone confirm that this problem also exists on Windows OS?

And there is GOOD NEWS: this buggerdebug is solved with update 7.0v2.

I don't know about you, but me personally, I'm going to build an appversion-check in every startupscript of my 7-databases.

I would never want my 7-database to be opened in 7.0v1!

Yep, fixed for me too in 7.0v2.

If there is a high risk of someone opening the file in 7.0v1, the workaround would be to use fields with globals instead of text objects... if there aren't too many, that is. The fields could be part of a completely separate table if necessary. This is how I had it set up until yesterday.

Thanks for confirming it.

Chris

Chris Baumbach said:If there is a high risk of someone opening the file in 7.0v1, the workaround would be to use fields with globals instead of text objects.

I don't think I will do that. I'm not going to build solutions to bugs that are fixed in a later version which one can obtain with a free download.

What I will do is make a start-upscript. This script will start every time a 7-database of mine is opened.

In this script I am going to check which FileMaker version is being used. And when this is 7.0v1 I will kindly inform the user that this database will not work with this version of FileMaker. And then I will shut down the database.

It will not be possible to use any of my 7-databases with 7.0v1.

You are right, that makes more sense.

Chris