Dave Crozier wrote:
Paul,
Just as a digression, why would you want to use plain array as opposed to a
property of a custom object as one such property could actually be the
array?
I find that ysing the custom object method really does allow a greater
degree of flexibility as named parameteres can actually be used as opposed
to parameters which are referenced by way of their array dimension.
Certainly changing the order/dimension of an array can involve you with a
great deal of recoding which is never a good thing.
I have retrofitted custom objects now to all my older forms which previously
used arrays and I'm glad of the ease in which I can now add/change parameter
names at will with minimum coding effort.
I must admit though that I've never used collections as parameters due to
the fact that I've never really looked into them in any detail I guess, but
they would seem to be useful in the same way as custom objects.
Just interested in your reasoning here.
Dave
I wanted to be able to call my FoxOpenFile form from the command window
and get an array of file names back. The method I described allows me
to call it like this:
DIME arrFileNames(1)
DO FORM FoxOpenFile WITH "arrFileames"
I believe that creating a custom object, giving it an array property
and passing it to the form would take an extra line of calling code
My post does answer the question that is asked from time to time - "How
do I return more than one value back from a form ?"
Cheers
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
