Ron Chestnut wrote:
>
> Yes, we all know that, or knew it at one time. And when it happens to an IOC
> far away, it becomes painful to identify generally as the problem, as well as
> finding the specific culprit if many changes were made.
>
> Could the code which does the check in IOCINIT be extracted and snuggled into
> a little utility for the developer which would check the CALCs in a given
> database and ease this tragedy??
If you uses either dct313 or gdct313 to read the .db file
any errors will be reported.
Also look at my next message.
Marty Kraimer
- References:
- Bad CALC record kills IOC Ron Chestnut
- Navigate by Date:
- Prev:
Re: Bad CALC record kills IOC Ralph Lange
- Next:
Re: Bad CALC record kills IOC Marty Kraimer
- Index:
1994
1995
1996
<1997>
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
Bad CALC record kills IOC Ron Chestnut
- Next:
Re: Bad CALC record kills IOC Bob Dalesio
- Index:
1994
1995
1996
<1997>
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
| 
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·