>>> >>>>I have purchase a report writer called FoxFire, to help me in
>>> reporting.
>>> >>>>Any comment on this product "FoxFire"?
>>> >>>
>>> >>>
>>> >>>FoxFire is great tool! It still uses the VFP Report
>>> Writer....internally. They've pulled apart the guts of the FRX and creat
>>> one on the fly. After all, it is just a DBF with a different extension.
>>> >>>
>>> >>>Craig
>>> >>
>>> >>Craig,
>>> >>
>>> >>Excuse me for butting in here, but I think that part of the problem
>>Alvin
>>> is experiencing may have to do with an unsupported paper size. This isn't
>>
>>> unusual for preprinted forms. If this is the case, I'm not so sure that
>>> FoxFire! can help, since it too would be at the "mercy" of the printer
>>> driver. The only solution I've ever found to this problem is a real
>>kludge
>>> for the report writer. The user has to specify that the printer is the
>>> Generic/Text Only driver when creating the report. They also have to
>>supply
>>> the control codes for it, as well as the paper size. Uggh!
>>> >>
>>> >>George
>>> >
>>> >George,
>>> >
>>> >I don't remember the original post indicating anything about paper size.
>>
>>> Just a question about FoxFire. I agree...preprinted forms cause a
>>problem.
>>> Does Crystal Reports handle odd paper sizes any better??
>>> >
>>> >Craig
>>>
>>> Craig,
>>>
>>> Absolutely right! He didn't mention anything about paper size. Two
>>things,
>>> however, led me to believe that this might be part of the problem as
>>well.
>>> One was the solution he was trying to implement. I've seen the old "count
>>
>>> lines and eject" technique used in a number of instances (rather than
>>> dealing with the report writer) where the author was trying to deal with
>>an
>>> odd paper size. Two, all I have to do is look at the small mountain that
>>> passes as my incoming bills to know that preprinted invoices/bills come
>>in
>>> a wide variety of sizes.
>>>
>>> Alvin's the only one who knows whether or not paper size is part of the
>>> problem. Just trying to save you some time and bucks, Alvin.
>>>
>>> I didn't mean to single FoxFire! out as not being able to handle odd
>>sizes.
>>> Frankly, I don't know for certain (see my "I'm not sure..." line).
>>However,
>>> I would suspect that neither it nor Crystal Reports can, since paper size
>>
>>> is in the domain of the printer driver. Of course, if either provided a
>>> complete set of printer drivers for this purpose, sure. I don't think
>>> that's too likely though.
>>>
>>> George
>>
>>Hi Craig and George, I'm very glad that both of you have given me a lot of
>>tips and feedbacks on the issue of reporting. Well, well.....there isn't
>>any
>>answer that who is right or wrong. I did mentioned that I welcome any
>>comments, in other words any suggestions may it be related or not, all
>>are welcome. Just feel free to discuss and I will take whatever I need.
>>
>>Sorry for any misunderstanding creared and I sincerely thank each and
>>every one of you in this VFP group for your contributions and great help.
>>
>>Cheers, Alvin 8-)
>
>Alvin,
>
>I don't think think that there was any misunderstanding. At least I hope not. Craig was (and is) correct. I was only trying to point out that in these types of situations, the programmer (in this case, you) often attempts to deal with the printer directly to overcome the problem of an unsupported paper size, and offer an alternative solution.
>
>Craig, I hope you didn't take my "Absolutely right!" the wrong way. If so, my apologies. The only intent was indicate (perhaps too entusiastically) that I agreed with you.
>
>Pax,
>
>George


No offense taken. This is one of the great things about the UT...we all offer advice...and others see things that we don't.

Craig