$0 - Report Main Lists using Inst Var
Chris Peck
chris-peck at wordmaster.com
Fri Jan 29 14:22:26 EST 2010
That is true, but it still has a notational path back to the window
and then to the method where it's declared, which is less distance to
go than an instance var would need. Thus, to my mind, if the command
can find a local variable using that path, it *should* be able to do
so for an instance variable also. But of course, it has to be taught
how to do this, and as format variables from Classic were converted to
class variables, they work fine, and local variables stayed local
variables, and they continue to work fine also. However, instance
vars are new to Studio, so there is no history behind the command's
code to work from, and I'm betting someone simply didn't do the job
behind said code for the Set Report Main List command to get it to
properly recognize inst vars without giving it a notational path. So
it causes me extra work now, but it isn't the first thing they did
poorly to cause me headaches. Luckily, there are enough other good
new things in Studio to make up for it.
Chris
On Jan 29, 2010, at 1:11 PM, Fred Brinkman wrote:
> your local variable is always a local variable
>
>
>
> Fred Brinkman
> www.euromnis.com
>
> **********************************************
> Fred Brinkman Consultancy
> B-1000 Brussels
>
> Tel. +32-474-83 80 80
> Fax +32-2-330 10 31 (on request)
> Email fred.brinkman at euromnis.com
> *********************************************
>
>
>
>
>
>
>
>
>
>
>
> Op 29 jan 2010, om 20:04 heeft Chris Peck het volgende geschreven:
>
>> I wonder how it figures it out when I'm using local variable then?
>>
>> Chris
>>
>>
>>
>>
>> On Jan 29, 2010, at 1:03 PM, Fred Brinkman wrote:
>>
>>> Your instance var looses scope the moment you go to the report, so
>>> the yell 'report list is not a list field' is correct, with $cinst
>>> you're always in the correct instance...
>>>
>>>
>>> Fred Brinkman
>>> www.euromnis.com
>>>
>>> **********************************************
>>> Fred Brinkman Consultancy
>>> B-1000 Brussels
>>>
>>> Tel. +32-474-83 80 80
>>> Fax +32-2-330 10 31 (on request)
>>> Email fred.brinkman at euromnis.com
>>> *********************************************
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> Op 29 jan 2010, om 19:56 heeft Chris Peck het volgende geschreven:
>>>
>>>> That works, Fred. So it seems that I might be right in that the
>>>> command internally doesn't follow the notation back to the window
>>>> correctly, unless you give it very literal direction. Arg, still
>>>> causes me extra work when I'm getting a window overhauled, but at
>>>> least I can keep the same basic construct with the addition of
>>>> the '$cinst.' added. Thanks for the suggestion.
>>>>
>>>> Chris
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> On Jan 29, 2010, at 12:37 PM, Fred Brinkman wrote:
>>>>
>>>>> did you try to set the report main list to $cinst.MyList
>>>>>
>>>>>
>>>>>
>>>>> Fred Brinkman
>>>>> www.euromnis.com
>>>>>
>>>>> **********************************************
>>>>> Fred Brinkman Consultancy
>>>>> B-1000 Brussels
>>>>>
>>>>> Tel. +32-474-83 80 80
>>>>> Fax +32-2-330 10 31 (on request)
>>>>> Email fred.brinkman at euromnis.com
>>>>> *********************************************
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Op 29 jan 2010, om 17:04 heeft Chris Peck het volgende geschreven:
>>>>>
>>>>>> Hi All,
>>>>>>
>>>>>> Has anyone found a way to use the Set Report Main List command
>>>>>> with an Instance variable list? Using ver 4.3.1.4 now, and
>>>>>> I've found that if I change a class list variable during my
>>>>>> window overhauls to an instance variable, the Set Report Main
>>>>>> List will then give an error that the main list field is not a
>>>>>> list field. To get around this problem, I've been declaring a
>>>>>> local var, then doing a merge, resetting the report main list
>>>>>> to the local var, and all works fine, but it's not a good long
>>>>>> term solution to the issue I've found. Also, does anyone know
>>>>>> if this issue has been forwarded to TL?
>>>>>>
>>>>>> Chris Peck
>>>>>> Software Developer
>>>>>> Word Master, Inc.
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> _____________________________________________________________
>>>>>> Manage your list subscriptions at http://lists.omnis-dev.com
>>>>>
>>>>> _____________________________________________________________
>>>>> Manage your list subscriptions at http://lists.omnis-dev.com
>>>>
>>>> _____________________________________________________________
>>>> Manage your list subscriptions at http://lists.omnis-dev.com
>>>
>>> _____________________________________________________________
>>> Manage your list subscriptions at http://lists.omnis-dev.com
>>
>> _____________________________________________________________
>> Manage your list subscriptions at http://lists.omnis-dev.com
>
> _____________________________________________________________
> Manage your list subscriptions at http://lists.omnis-dev.com
More information about the omnisdev-en
mailing list