I do the same. After all there could be a need for a server restart. I also
trigger them to reload every day in case data changes. Last thing I do in
the tcf is set a domain scope date and custom scope date.
--
Dan Stein
FileMaker 7 Certified Developer
Digital Software Solutions
799 Evergreen Circle
Telford PA 18969
Land: 215-799-0192
Cell: 610-256-2843
Fax 413-410-9682
FMP, WiTango, EDI,SQL 2000, MySQL, CWP
[EMAIL PROTECTED]
www.dss-db.com
"There is a larger frame to the painting than the one that bounds our
life's events."
> From: Robert Garcia <[EMAIL PROTECTED]>
> Reply-To: "[email protected]" <[email protected]>
> Date: Fri, 25 Aug 2006 09:22:30 -0700
> To: "[email protected]" <[email protected]>
> Subject: Re: Witango-Talk: VariableTimeout auto assign?
>
> They used to, in 5.0, and with 5.0 we built our strategies around it.
>
> I have never been comfortable, with ASSUMING a domain var is
> populated correctly, so we tested heavily the process of checking the
> vars on each execution, which was so fast, it was almost
> immeasurable. So from the time forward, with witango, we have a
> policy in code, that on each execution, a process verifies that our
> domain objects are initialized. Even though they are called on server
> startup. We don't necessarily check each domain var, but if I know my
> initialization method, sets many at once, we may just check one, or
> check the object status, that created all of them, all of our domain
> vars are managed in TCFs.
>
> --
>
> Robert Garcia
> President - BigHead Technology
> VP Application Development - eventpix.com
> 13653 West Park Dr
> Magalia, Ca 95954
> ph: 530.645.4040 x222 fax: 530.645.4040
> [EMAIL PROTECTED] - [EMAIL PROTECTED]
> http://bighead.net/ - http://eventpix.com/
>
> On Aug 25, 2006, at 8:53 AM, Dan Stein wrote:
>
>> I thought the domain scope variables along with custom scope
>> persist unless
>> the server is restarted I did not think they timed out.
>>
>> --
>> Dan Stein
>> FileMaker 7 Certified Developer
>> Digital Software Solutions
>> 799 Evergreen Circle
>> Telford PA 18969
>> Land: 215-799-0192
>> Cell: 610-256-2843
>> Fax 413-410-9682
>> FMP, WiTango, EDI,SQL 2000, MySQL, CWP
>> [EMAIL PROTECTED]
>> www.dss-db.com
>>
>>
>> "It's very hard to grow, because it's difficult to let go of
>> models of
>> ourselves in which we've invested so heavily."
>>
>>
>>> From: Scott Cadillac <[EMAIL PROTECTED]>
>>> Reply-To: "[email protected]" <[email protected]>
>>> Date: Fri, 25 Aug 2006 09:20:00 -0600
>>> To: "'[email protected]'" <[email protected]>
>>> Subject: Witango-Talk: VariableTimeout auto assign?
>>>
>>> Hi Folks,
>>>
>>> I apologize that I'm not staying as up to date as some of you with
>>> Witango
>>> programming, but could someone correct me if I¹m wrong, but
>>> shouldn't a
>>> VariableTimeout variable be automatically assigned to each
>>> variable scope?
>>>
>>> I have several sets of domain scope variables (in a multi-domain
>>> system using
>>> a single set of TAF files), and I noticed that some of the domain
>>> scopes don't
>>> have a VariableTimeout variable.
>>>
>>> Shouldn't there automatically be one when any domain scope var is
>>> assigned? Or
>>> have I totally lost my marbles?
>>>
>>> The documentation doesn't explicitly say this, but is implied with
>>> "The system
>>> scope version of this configuration variable determines the
>>> default period, in
>>> minutes, after which domain and user variables expire."
>>>
>>> Running 5.5.009 Liquorice (Win32) on Windows 2003.
>>>
>>> Calling @@Domain$variableTimeout returns an empty value, and is
>>> not in the
>>> <@VARNAMES SCOPE=domain> list.
>>>
>>> Thank you in advance.
>>>
>>> Scott Cadillac,
>>> Email: [EMAIL PROTECTED]
>>> http://scott.cadillac.bz
>>>
>>>
>>> _____________________________________________________________________
>>> ___
>>> TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
>>>
>>
>>
>> ______________________________________________________________________
>> __
>> TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
>
> ________________________________________________________________________
> TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
>
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
