PHP and filepro - login lesson

[Richard Kreiss]

Coming from a business background to programming made the transition easier as I had a basic understanding of how many companies operated. I manufactured and sold to large and small retailers as well as Distributers. As a manufacturer I also dealt directly with my suppliers. Although I was(am) 8 credit hours away from a degree in accounting, I have stayed away from even attempting to write this type of software. For those clients who waned accounting software, I usually recommended Quickbooks. As most of my client’s were factored, they did not require a receivables program. For those who did, I had a non-accounting A/R type of program. Most of the time this was for commissions owed. 

Most of my programs were written with the user in mind. I would endeavor to make things simpler and have the workflow 
The same as or similar to what they were used to. The issue I ran into was usually about 90 days after the program was installed. They would ask If the program could run faster. Mostly this was for printing. When I would put a stopwatch on the print job, filePro was creating output as fast as the laser printer could print. I tend to use dash lookups whenever possible to speed up record selection. 

There is only one output I will not touch as I didn’t write it and as often as I have look I still don’t understand it. 

Richard
Sent from my iPhone

> On Apr 15, 2018, at 2:15 PM, Fairlight via Filepro-list <filepro-list at lists.celestial.com> wrote:
> 
> On Sun, Apr 15, 2018 at 10:34:44AM -0700, Bill Campbell via Filepro-list thus spoke:
>> 
>> I'll take this a step further, most programmers don't seem to
>> have a clue about workflow and business procedures so write code
>> that's difficult to use and error prone.  FilePro makes it pretty
>> easy for somebody who knows his business to create mostly working
>> systems without having to have a lot of programming skills.
> 
> Entirely true, in my experience.
> 
> It helps having been an office temp engaged in hardcore data entry.  You
> got to know what works and what doesn't, what's efficient and what's not.
> For as much as I hated it, some of the CICS-based systems I used were
> actually some of the best-designed.
> 
> The hardest part of programming has never been about learning the
> languages.  The hardest part is learning the business for which you're
> coding.  That can be a years-long endeavour, depending upon business
> complexity.
> 
> There's a danger in knowing -either- side of the equation without knowing
> the other half.
> 
> mark->
> -- 
> Audio panton, cogito singularis.
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> Subscribe/Unsubscribe/Subscription Changes
> http://mailman.celestial.com/mailman/listinfo/filepro-list