Good things are worth waiting for:)

In the meantime I will push on with an idea I have for simplfying using arrays in the report designer. It drives me nuts having to identify each element on a busy report. myarray(1),myarray(2),myarray(3)etc...(this can be hundreds of times)

Creating the arrays is simple enough with select into array so I hope to create a simple udf along the lines of.

arrayput('aCustomer')

Each time the above is called it will return the next element of the array.
So now I just paste the above mutiple times into the right places and I dont have to edit each occurance to increment its index number.

Not as easy as dragging a grid onto a form but it gets me there in the end.






>>Wow Nadya that would be so handy:)
>>
>>Please try and translate it. We only need a rough idea of how it works.
>>You have some smart cookies in Russia:)
>
>I posted a message at this forum. However, there could be some problems. For instance, she may not be reading this forum often, so she can miss this message. If she would not reply in two days, I'll ask permissions to take solution and post on other forums. Just to low your expectations a little bit, it may take a week, before this solution would be posted. I also didn't test it, so I don't really know, how it works.
>
>Anyway, hopefully we can come to something soon.
>
>
>>
>>Hi Mark,
>>>
>>>Recently in Russian VFP Club forum was discussed the same problem. Nataly, who was working on it, finally came out to a solution and posted it on this forum. Unfortunately, I'm afraid, the comments would be in Russian. I can ask her to send me this solution and may be translate comments into English. Or may be she can post it here in Download section. It may take couple of days, if she would agree, of course.
>>>
>>>>In order to overcome some of the limitations of the Report designer I did some lateral thinking and decided to use the Form Designer with Steven R Ruhl's form printing program.
>>>>
>>>>Let me explain my problem.
>>>>
>>>>I often have to produce reports that must display a variety of small tables all on the one page. Some next to each other, some underneath each other. As we all know VFP does not allow sub reporting zones.
>>>>
>>>>These tables usually have a fixed number of records so in the past I have created them in a couple of different ways as follows.
>>>>
>>>>1. Concatanate all the records/fields into a memo field with a chr(13) at the end of each record and place the memo field anywhere I want in the report designer. Nice and easy but need to use fixed width fonts and cant draw lines in between the records and fields
>>>>
>>>>2. Scatter everything into one large array and place each element in the array where I want it in report designer (can draw lines around things this way, but boy is it tedious)
>>>>
>>>>3. A variety of strange manipulations with select statements and print when in report designer (UGH!)
>>>>
>>>>4. Using @SAY :(
>>>>
>>>>After ruling out external progs such as Crystal Reports ,Excel and Fineprint I decided there must be a way to do this in straight VFP
>>>>
>>>>Since Steven R Ruhl's form printing/capture class make printing a form easy I decided to create a blank form and drop a few grids on it set all the properties so that the form and grids look like a printout (white backgrounds) and then print out the form.
>>>>
>>>>This almost worked <g>
>>>>Trouble is the class only wants to print the part of the form that is visible in the desktop viewing port. Any part of the form that ends up off the desktop does not get printed.
>>>>
>>>>I can do the report in 2 halves each of 800 x 600 using capture instead of print and then print the 2 halfs as images in a normal report but since I wanted to turn this technique into a form based class that others can use just by dropping some grids and labels onto, everything starts to look too fiddly.
>>>>
>>>>Also I had hoped to do all this in the background but it seems the form has to be visible for printing or capture anything to happen (yes I know).
>>>>
>>>>This could be a very useful feature if someone can get past these limitations since it would be possible to produce some very fancy (though limited) reports using this method. Maybe even something fancier would be possible with reporting style grid classes resizing to fit their number of records (I dont want to go there myself)
>>>>
>>>>All help gratefully received.
>>>>Or maybe just write it for me since I am getting a bit fed up with the idea <g>