A suggestion
Richard Kreiss
rkreiss at gccconsulting.net
Fri Apr 8 07:29:46 PDT 2016
Some of you may have done this already by I have a suggestion which make coding easier.
I have a directory (folder) I call sub. I keep small program routines (processing table) here and import them when I need to use the code. One example is on I call tabs, I use this one to control which field a left tab, arrow, up arrow, etc moves the cursor to. This is especially true when this is a "must fill" field handled in programming at @wlfxx.
I have an @once routine which I need to use in all programs for one client which checks if the user has permission to run this type of program. It consists of 10 line of code I don't constantly have to rewrite and I can easily load it from any filePro file.
For those old time filePro programmers, I have a copy of the "zoom" routine which predates the browse llookup.
I also have a routine I used when computers were very slow. It creates a "thermometer" type display so the user could see that records were being processed. The 2 places I used this were for outputs so the user had an idea of where the program was and about how long the output would take. The other place was with a browse lookup which used a drop. This routine lept the user from thinking the program got "hung up". With today's computers this routine is almost unnecessary. I could add this programming to that output which process a few million records.
I do have a routine similar to the one Ken showed a long time ago, which allows for the resizing of a memo window once it is open in I-U mode on a record.
One other handy program I wrote is one I call "viewer". This is a filePro program which allows me to view a processing table (ASCII) when you have exceeded your development license value. I had this problem on my laptop when I had only a single user development license. This is written for windows and uses Notepad to display the processing table. If you are accustomed programming with a text editor, the processing table can be edited. This is especially handy if you need a global search and replace routine which is missing from the filePro editor.
Richard
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.celestial.com/pipermail/filepro-list/attachments/20160408/68b2b2b5/attachment.html>
More information about the Filepro-list
mailing list