Everyone who has replied so far.
Thanks

I am still struggling with this, but I am now closer, and have some 
direction, I'll report back my final solution.

The actual implementation I am working on is :
In a component, a method which can build 1 or more arrays of table and 
field information from the structure of the host.
Maybe I am too ambitious...

(from Host)
  
Build_Table_Arrays(->$Table_Names_array;->$Table_num_array;->$Table_Pointer_array)
This call would build 1D arrays with the (respectively) table names 
(formatted for users), Table numbers, and pointers to the tables.

The 'trick' is that I want to allow a slightly different call to the 
same component method
  
Build_Table_Arrays(->$Struct_Names_array;->$Struct_num_array;->$Struct_Pointer_array)
Where $Struct_xxxx is a 2D array which will contain not only Table, but 
also field information; so the resulting arrays would contain 
(respectively) ALL table and field names (formatted for the users), ALL 
Table and Field numbers, and pointers to ALL tables and Fields.

And this is where the dereferencing a pointer to a 2D array, sub-array 
access problem is occurring, inside the component method and it's 
internal method calls for parameter validation (my post on Type issue), 
and for resizing the sub-array(s) for field information (this post).

<Irony on>  
*Of course* 
</Irony off> 
the methods in the component that do type validation, and array 
resizing ALL require pointers as parameters, because these methods are 
themselves ALSO exposed as part of the Utility component package I am 
trying to create....   :)

... and now my head hurts again...
:)

Thanks
Chip




---------------
Gas is for washing parts
Alcohol is for drinkin'
Nitromethane is for racing 
**********************************************************************
4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4d.com/archives.html
Options: http://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:[email protected]
**********************************************************************

Reply via email to