QuickStart Development

[Kenneth Brody]

On 6/15/2016 10:54 AM, Nancy Palmquist via Filepro-list wrote:
[...]
> A footnote to remember is that while every effort is made to make filepro
> and Quickstart filepro run exactly the same on the same tables it is not
> always the case.  It is critical that you compile the tables with the
> associated automatic table indicated.  I have seen differences in how they
> throw error messages and like issues over the years.  So it is important to
> test your software in both environments.  QS does not have a debugger level
> so you will have to get very friendly with logtext to track your flow.
[...]

If you have a dummy field which is defined in automatic processing, but not 
in the auto processing to be used for the output, and you use that dummy 
field for multi-level break subtotals[*], then you will get different output 
in rreport than in dreport.  I don't recall if there is a problem with a 
dummy field not defined in automatic, but defined in the auto processing 
used for the output.  (rclerk-vs-dclerk is not affected.)

There have been a few bugs over the years where Quikstart would crash in 
some instances.  Those have been fixed when encountered.

I've heard people say that there were other differences where quikstart gave 
difference results than plus, but I don't recall what they were, or if 
anyone ever sent such a file to fpsupport to duplicate.



[*] In case anyone here has forgotten, filePro dummy fields can be used for 
multi-level break handling "automagically".  For example, a simple 
processing line of:

     xx(10,.2) = xx + sales

and placing "xx" on different subtotal break levels on the output will give 
the subtotal for "sales" for that break level.  Place it on the detail line, 
you get the sales for that particular record.  Place it on the "customer" 
subtotal break, and you get the total sales for that customer.  Place it in 
grand total, and you get total sales.  Same report, same "*xx", different 
(sub)totals.

-- 
Kenneth Brody