Dorothy,

try to repair the table and the print-table
memo and blob fields are dangerous for table stability

Günter
Am 07.03.2011 05:38, schrieb Dorothy Keyser:
> Liz -- Thanks for your suggestions.  I have done all of those things, and
> it hasn't helped.
>
> Liz McGuire<liz@paradoxcommunity.com>  wrote:
>> Dorothy,
>>
>> Are the records in a tableframe or an MRO, or ...?
>>
>> Have you tried sizing the fields exactly how you need them, esp. the
>> graphic field, and then using Pin Horizontal and Pin Vertical?  And
>> turning off Size to Fit?
>>
>> Have you made sure that Word Wrap and Fit Height are in sync (either
>> both checked or both unchecked)?
>>
>> If in a tableframe and you have two objects (e.g. field and graphic, two
>
>> fields) in the same column, be sure to put them in a group.
>>
>> Those are the only things I can think of that might impact a report like
>
>> you describe.
>>
>> Liz
>>
>>
>> On 05 Mar 2011 21:31, Dorothy Keyser wrote:
>>> I am using Paradox 11 under Windows 7.  I am working with a
>>> database with 4400+ entries, each one including a picture -- .gif
>>> or .jpg depending on when it was entered.  I've been working on
>>> this thing for about twenty years.
>>>
>>> I have created a report that seems to do exactly what I want it
>>> to, except that 1) when I run the report, I get overprints with
>>> some of the fields -- and they don't seem to be the same entries
>>> every time I run the report, and 2) when I try to print the report
>>> to a printer or to a .pdf, some of the formatting gets lost -- especially
>>> the line squeeze and field squeeze formatting.
>>>
>>> Any help would be greatly appreciated.
>