on further investigation it seems to be only this one database . . . what could be so special about it??
I guess the database must have been corrupted somehow.
Even though a consistency check said everything is okay, I ran a Recover on the file and now it doesn't exhibit the issue.
Sorry for any alarm, well my alarm really.
It could be that just that one layout is damaged. You might try just replacing that layout with a new copy made from scratch. (Don't copy objects from the possibly bad layout.)
That's a better option than replacing your current copy with the recovered copy.
Things to keep in mind about Recover:
- Recover does not detect all problems
- Recover doesn't always fix all problems correctly
- Best Practice is to never put a recovered copy back into regular use or development. Instead, replace the damaged file with an undamaged back up copy if this is at all possible. You may have to save a clone of the back up copy and import all data from your recovered copy to get a working copy with the most up to date information possible.
That's kinda worrisome, I mean I'm in the middle of so many changes that I don't know if I could find a backup that isn't really missing a lot of work.
I thought FM was a lot more robust than that.
I was looking at the recover.log and near the end it indicates (similar to what you wrote)
Recover built a new database without detecting any problems. It would be safest to copy only the most recent work from the recovered file into a backup copy of the original file, instead of using the recovered file going forward.
Note: Recover only checks the data blocks of the file and generates a new file from that data. The Consistency Check checks all blocks of the file, and may find more problems in the original file than Recover does.
I did do a consistency check and it indicates there are no errors . . . should I feel any better?
I'm reading more things about which i don't have any experience.
Saving as "Compacted". I'm able to do this with this file.
Do I feel better now?
Hi, I have one layout that exhibits the same behavior, but only occasionally. I don't believe the layout is corrupt and have no other problems with the file. This particular layout is a Revenue Canada tax form (T4A) and much of it was generated from a PDF supplied by them. Every once in a while the distortion occurs. It's a two-page layout (hence the scrolling) with many fields. I may be wrong, but I don't worry about it. Simply entering Browse mode and going back to Layout mode seems to work. RW
I use FM Pro11 adv. (german) and have the same bug. If you use the "button" in the scroll-bar it works bad but if you click into the scroll-bar it works fine.
Fix around is to disable (being in Layout mode) in german: Seitenränder in english should be "page margins" under the menu "Ansicht" (german) "View" (? english).
What you describe seems similar to an issue that has bee reported previously:
For More Information see: Edit Layout/Report in Pro 11 Screen turns to gray when using either of the scroll bars.
This is one of many acknowledged bugs that can be found in the Known Bug List here in the Report an Issue section of the forum.
It can also be downloaded as a database file from: http://www.4shared.com/file/8orL8apk/FMP_Bugs.html