Hi Rauf, Yes we have no arrays. Here are some solutions that I have implemented in the past.
Whenever it is setup data that you would normally put in processing options, you can use one field and separate the values (CSV-like), or you can bite the bullet and put in 10 (or more) proc. opt. fields in the PO template. Both of these methods make it a little more difficult to code for (parsing and referring to each PO name) and more difficult to populate by the user (having to remember to format with commas or checking all the fields each time). I typically create a setup table with a unique identifier for the general key with a counter for each repetitive line (kinda like an array) and build an application around it (doesn't really take that long). This way users can set up several options at once and then all they have to do is put a processing option for the unique identifier in the template.
If the array is for information being passed between forms or form to report, then I use the same method only I call it a work file where I create a unique ID and pass the ID between control objects. This is basically what the original cache options would fall back on when the memory functions were still being worked out. I think. Anyway, many of the MBFs still have an option to use memory or workfile depending upon a flag value.
Ben again,