Printing problem on Windows machine

[Timothy Miller]

  Hi Sarah,

The wise and generous person subscribes to the list. I think I'll 
hand your question off to him. He might prefer to post his own script.

I'll quote the brief description he sent to me. I don't think he'd mind:

>The way it basically works is to copy each field from the card to a 
>printing stack. If a field is larger than a page, then it creates a 
>second card in the printing stack and copies the large field to that 
>card. It then divides up the text between the two fields in the 
>printing stack. It continues this process until enough cards with 
>copies of the large field have been created to hold all of the text 
>without any of it getting lost.


I'm not sure whether the script uses

Actually, printfield seems to work okay in Windows, as long as the 
printed output is no longer than one page. The printer goes crazy on 
page two and subsequent pages.

If I understand the suggested script, the general approach is to use 
"Print Card" or "Print Stack" instead of printfield. As far as I can 
tell, Print Card works fine on my Windows machine, as long as I get 
the print rect and printmargins right.

There are probably other workarounds. For instance, it might be 
possible to shuttle lines in and out of the field, so it never 
contains more than one printable page, then use printfield 
repeatedly, then replace the original text when printing is 
completed. I don't know -- haven't tried that.

Any other ideas?

What a pain in the neck! It would be WAY easier to start using my 
friendly Macintosh again. I had some other reasons to try my stacks 
on my Windows machine, but it might not be worth the trouble, and 
it's probably bad karma.

I hope this was a teensy bit helpful.


Cheers,


Tim

>  > A wise and generous soul has sent me a private message, including a
>>  model script necessary to print fields more than one printed page
>>  long, on a Windows machine. I'd suppose this has been discussed to
>>  death, so I'll let it rest.
>
>Hi Tim,
>
>Could you quote the script here so it is available to us all? I don't
>need it at the moment, but as another Mac person, I might run into
>this problem at some stage, so I would love to be able to find this in
>the archives.
>
>Thanks,
>Sarah