sequence of lines

[ASJ Botenga]

op 03-06-2008 04:02 schreef David Thompson op dthmpsn1 at illinois.edu:

>> if Macro disturbs people I won't use it anymore.
> 
> I don't find Macro disturbing. I was simply using it as a clue. That,
> plus the fact that you are using an email program that doesn't run in
> OS X, made me wonder if it would be a waste of time to recommend
> features such as custom statements and functions, which aren't
> available for versions prior to Panorama V.

I am somewhat puzzled by your remark it doesn't run in OS X, because here it
runs alright even in Leopard's latest version. Regarding your second remark
please note (below) that I have access to the latest version, so it is/was
certainly no waste!

>> Panorama 3.1.5, the last version with active 'Equations' in the Design Sheet,
>> witch is highly essential for, and extensively used by me, but have access to
>> the latest version.
> 
> This feature still exists in the latest versions. Some versions may
> have had some bugs, when U.S. Procedures & Formulas weren't being
> used. I think those problems have been worked out, but someone
> outside the U.S., like Kurt Meyer, would know more about that than I
> do.
That is comforting
 
>> Variables exist to give your procedures as many
>> "memories" as they require. A procedure that
>> needs 100 memories can declare 100 variables.
> Is it not so that the unique value of the clipb. for procedures remains the
> possibility to copy, like a chameleon, date, text or numeric data from a
> database and paste these on other lines in any given field.
> 
> This is partly true. When you copy and paste, the data type
> conversions are done for you. If you use a variable to hold the value
> while you move to another record, you need to use the appropriate
> function to do the conversion. For example: Instead of
> 
> Field "DateField"
> Copy
> DownRecord
> Field "TextField"
> Paste
> 
> you could use
> 
> Local theDate
> theDate = datepattern(DateField, "DD-MM-YYYY")
> DownRecord
> TextField = theDate
Sure, but, if I may refer to previous remarks, that text is longer.
The first example I write, perhaps a bit unusual, in one line, actually even
a part of a 'procedure-line':

field date copy downrecord field a paste

I may add that for my extensive procedures I change, my incidentally large,
fieldnames in characters (alphabetical) by which I can spare a lot of text.
Naturally I have to restore that at the end.
Furthermore, I use the clipb. many many times in my procedures also to cut
lines etc. Therefore it is less essential for me to preserve the contents.
It is probably possible to keep the clipb. unchanged during the running of a
long Procedure, in witch I sometimes make new lay-outs (others than provided
by forms), but that will multiply the length of its text.

May I conclude with a question I forgot to ask previously.
Are text funnels which I find most helpful also obsolete

Allard