O$: $ctask problem with Multiple Libraries

David Swain dataguru at polymath-bus-sys.com
Thu May 15 16:26:40 EDT 2008

Hi Ray,

I wrote a series on various issues with tasks a couple of years ago  
for Omnis Tech News, which might be of use to you. Here are the  
titles and links:

"Task Basics" (28 Apr 2005) <http://www.omnis.net/technews/042805/>

"Multiple Task Processes" (26 May 2005) <http://www.omnis.net/ 

"Providing Global Resources in Multiple Task Applications" (23 Jun  
2005) <http://www.omnis.net/technews/062305/>

"Closing Instances and Tasks" (11 Aug 2005) <http://www.omnis.net/ 



David Swain

On May 15, 2008, at 12:30 PM, Ray Briggs II wrote:

> I have a main library that contains my Order window and I have a  
> separate
> custom library for a customer that runs an import and then opens  
> the Order
> window via an object call. The object call looks like this
> If tSecurity.$access(1)=kTrue
>      <Open Order Window>
> End If
> tSecurity is a task variable defined in my main lib. When I make  
> the call
> from my custom library the task variable is unknown, I assume  
> because $ctask
> is still pointing to my custom libs task. Is there any way to get  
> around
> this? It's not uncommon for a custom lib to make a call to the main  
> library
> and there could be more task variables there.
> I tried changing the $activetask but it didn't solve the problem.

More information about the omnisdev-en mailing list