![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
In fp5 I had several text calculations that incorporated tab characters and displayed nicely, but they're acting funny in fp7. Displayed in browse mode, tab characters sometimes appear correct, sometimes as 444 (a string of three fours) and sometimes as 000 (a string of three zeros). What's more, I can get all three results on the same layout using the same field duplicated three times, so that even though the formatting and everything else is exactly the same, the display result is tab in one field, 444 in another and 000 in the third. I've searched this group all the way back to 2000 and tried everything that's been written about inserting tab characters into calculations, so let me eliminate a few solutions: 1. Tab characters pasted into calculations from word processors do in fact appear to be tab characters, but only in the define fields options dialog. The actual calculated result usually appears as 444 or 000. 2. I've tried referencing a global text field that contains a tab character in my calculations, but get the same result as with the tab pasted into the define fields options dialog: it sometimes returns a tab, sometimes 444 and sometimes 000. 3. Using "/t" in the calculation just returns /t as a result. 4. The issue exists in three separate files, none of which are related, two of which have been made from scratch in FP7, one that was converted from FP6, and none of which have ever crashed -- so it's not a question of file corruption. I find this problem vexing. Any suggestions? Is anyone else experiencing it? Your combined wisdom would be greatly appreciated. FYI, I'm using FMP 7.0v3 on Mac OS 10.3.9. |
#3
| |||
| |||
|
#4
| |||
| |||
|
|
Hi, Harry - Thanks for taking a shot at this, because we've cracked it. I began this reply by listing why each of your solutions wasn't correct, but when I was addressing your mention of strange formatting options, it suddenly occurred to me, what if it's a fill character? If that were the case, each tab would display with exactly the number of fill characters that fit into the space, which in this situation happened to be three. Sure enough, the fill character for each tab was set to 4 on one of the fields and 0 on another. I can't believe I spent so many hours trying to crack this. But the real question is, why would three fields, each the duplicate of the other (as in command-D; as in, option-drag; as in, never accessed the text formatting dialog, let alone the _tab_ dialog three levels down), suddenly set all the tab stops to 0 or 4? Doesn't make sense. Is there a key combination I inadvertently pressed that sets tab fill characters? Seems unlikely. Nonetheless, I'm hugely relieved to have this solved. It was a real time-burner. |
)
#5
| |||
| |||
|
![]() |
| Thread Tools | |
| Display Modes | |
| |