Author: Dave Crozier
Posted: 2016-08-23 at 10:18:20
Ted,
Yes, that was the first thing I tried.... no effect...
I have also tried declaring oCollection_X as a public variable in the mainline stub even though it is never called just to remind the compiler that it does exist... again no joy I am afraid.
Dave
-----Original Message-----
From: ProFox [mailto:profox-bounces@leafe.com] On Behalf Of Ted Roche
Sent: 23 August 2016 16:13
To: profox@leafe.com
Subject: Re: Weird Compilation error
On Tue, Aug 23, 2016 at 10:45 AM, Dave Crozier <DaveC@flexipol.co.uk> wrote:
>
> All the coding works despite this damned error being thrown at compile time and I have tried all types of External commands thinking that the oCollection not being found could be fixed as you do with external arrays. However there isn't an "External Collection" command... so I am now stuck!
>
I'd use:
EXTERNAL ARRAY oCollection_X
in the myRefresh() code
But it sounds like you've tried that. Each method in a VCX is essentially compiled separately, so the EXTERNAL command is local to each snippet.
--
Ted Roche
Ted Roche & Associates, LLC
[excessive quoting removed by server]
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/18725B8CD2D5D247873A2BAF401D4AB290267263@EX2010-A-FPL.FPL.LOCAL
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.