Re: tiling two objects vertically
Salad wrote:[color=blue]
> Bradley wrote:
>[color=green]
>> Salad wrote:
>>[color=darkred]
>>> Bradley wrote:
>>>
>>>> WindAndWaves wrote:
>>>>
>>>>
>>>>> Thanks Bradley
>>>>>
>>>>> I tried that, but it seems that only reports can be embedded as
>>>>> subreports and forms only as subforms. We are mixing here, that
>>>>> is a subreport in a form does not work
>>>>>
>>>>> I think I need to set the size of each window or something like
>>>>> that, but I am not sure how.
>>>>
>>>>
>>>> Hmm, ok.
>>>>
>>>> The next question I have is "why?". Why do you need both open at
>>>> once? Can't you put the control of your form on the report?
>>>> (Haven't tried it myself:)
>>>
>>> A fruitless question. Why someone wants to do something is
>>> irrelevent.[/color]
>>
>>
>> Not at all! Knowing why allows you to determine if there is a better
>> way of doing it. You must always understand why a client needs
>> something. It's an important part of the analysis.
>>
>> <snip>[/color]
> True enough. However, why someone wants to do something, especially
> in NG questions, is most often irrelevant. There may be reasons why
> they want to do it one way and not another. I have posed questions
> before and the people answering me tend to wonder why I want to do
> something more than simply answering a question. When the question
> is about methods then you get into a long drawn out explanation of
> why you want to do something. If it is a question by someone that is
> a relative newbie to a feature of the system, OK. But if someone
> knows the product and how it works, there may be underlying reasons
> why a way of implementing something is done.[/color]
The reply from the person whom I asked shows exactly why it was a
fruitful question to pose. :)
[color=blue]
> In my responses, because I have asked in the past for some advice
> normally beyond the scope of what I know of a product, I tend to not
> focus on why something is being requested one way but answering the
> question. IOW, I may provide a recommendation for a better method to
> accomplish a task I may think may assist, but as to why they want to
> do something I tend to find a waste of time.[/color]
Everything a clients wants starts with a purpose (which is the "why").
Sure, I may think of a solution and then seek help in implementing it if
I have trouble. But if I also explain the "why" I may learn a whole new
way of looking at it at the problem at same time:) (ie. instead of
focusing on a single problem, look at the entire issue).
Holistic development LOL
-
regards,
Bradley
Salad wrote:[color=blue]
> Bradley wrote:
>[color=green]
>> Salad wrote:
>>[color=darkred]
>>> Bradley wrote:
>>>
>>>> WindAndWaves wrote:
>>>>
>>>>
>>>>> Thanks Bradley
>>>>>
>>>>> I tried that, but it seems that only reports can be embedded as
>>>>> subreports and forms only as subforms. We are mixing here, that
>>>>> is a subreport in a form does not work
>>>>>
>>>>> I think I need to set the size of each window or something like
>>>>> that, but I am not sure how.
>>>>
>>>>
>>>> Hmm, ok.
>>>>
>>>> The next question I have is "why?". Why do you need both open at
>>>> once? Can't you put the control of your form on the report?
>>>> (Haven't tried it myself:)
>>>
>>> A fruitless question. Why someone wants to do something is
>>> irrelevent.[/color]
>>
>>
>> Not at all! Knowing why allows you to determine if there is a better
>> way of doing it. You must always understand why a client needs
>> something. It's an important part of the analysis.
>>
>> <snip>[/color]
> True enough. However, why someone wants to do something, especially
> in NG questions, is most often irrelevant. There may be reasons why
> they want to do it one way and not another. I have posed questions
> before and the people answering me tend to wonder why I want to do
> something more than simply answering a question. When the question
> is about methods then you get into a long drawn out explanation of
> why you want to do something. If it is a question by someone that is
> a relative newbie to a feature of the system, OK. But if someone
> knows the product and how it works, there may be underlying reasons
> why a way of implementing something is done.[/color]
The reply from the person whom I asked shows exactly why it was a
fruitful question to pose. :)
[color=blue]
> In my responses, because I have asked in the past for some advice
> normally beyond the scope of what I know of a product, I tend to not
> focus on why something is being requested one way but answering the
> question. IOW, I may provide a recommendation for a better method to
> accomplish a task I may think may assist, but as to why they want to
> do something I tend to find a waste of time.[/color]
Everything a clients wants starts with a purpose (which is the "why").
Sure, I may think of a solution and then seek help in implementing it if
I have trouble. But if I also explain the "why" I may learn a whole new
way of looking at it at the problem at same time:) (ie. instead of
focusing on a single problem, look at the entire issue).
Holistic development LOL
-
regards,
Bradley
Comment