comp.lang.cobol

• Date Index

---

• How to find the greatest of two numbers without using the comparison operators?, Aparajita
  • Re: How to find the greatest of two numbers without using the comparison operators?,
  • Re: How to find the greatest of two numbers without using the comparison operators?, Pete Dashwood
    • Re: How to find the greatest of two numbers without using the comparison operators?, Aparajita
      • Re: How to find the greatest of two numbers without using the comparison operators?, Michael Mattias
      • Re: How to find the greatest of two numbers without using the comparison operators?, SkippyPB
      • Re: How to find the greatest of two numbers without using the comparison operators?, Pete Dashwood
    • Re: How to find the greatest of two numbers without using the comparison operators?, William M. Klein
      • Re: How to find the greatest of two numbers without using the comparison operators?,
      • Re: How to find the greatest of two numbers without using the comparison operators?, Howard Brazee
  • Re: How to find the greatest of two numbers without using the comparison operators?, Howard Brazee
  • Re: How to find the greatest of two numbers without using the comparison operators?, Frank Swarbrick
    • Re: How to find the greatest of two numbers without using thecomparison operators?, Rick Smith
      • Re: How to find the greatest of two numbers without using thecomparison operators?, William M. Klein
  • Re: How to find the greatest of two numbers without using the comparison operators?, SkippyPB
• OT: Baby Update (final), Pete Dashwood
  • Re: Baby Update (final), Charles Hottel
    • Re: Baby Update (final), Robert Jones
      • Re: Baby Update (final), Charles Hottel
  • Re: OT: Baby Update (final),
    • Re: OT: Baby Update (final), Charles Hottel
    • Re: OT: Baby Update (final), SkippyPB
      • Re: OT: Baby Update (final), Charles Hottel
  • Re: OT: Baby Update (final), Doug Miller
    • Re: OT: Baby Update (final), Charles Hottel
• Compiling forward references, Robert
  • Re: Compiling forward references, Pete Dashwood
  • Re: Compiling forward references, Rick Smith
• SAME AS ('02 Standard) Clause - and circulatiy, William M. Klein
  • Re: SAME AS ('02 Standard) Clause - and circulatiy, William M. Klein
    • Re: SAME AS ('02 Standard) Clause - and circulatiy, Rick Smith
      • Re: SAME AS ('02 Standard) Clause - and circulatiy, William M. Klein
      • Re: SAME AS ('02 Standard) Clause - and circulatiy, Rick Smith
      • Re: SAME AS ('02 Standard) Clause - and circulatiy, Rick Smith
  • Re: SAME AS ('02 Standard) Clause - and circulatiy, Pete Dashwood
  • Re: SAME AS ('02 Standard) Clause - and circulatiy, Rick Smith
    • Re: SAME AS ('02 Standard) Clause - and circulatiy, William M. Klein
      • Re: SAME AS ('02 Standard) Clause - and circulatiy, Rick Smith
      • Re: SAME AS ('02 Standard) Clause - and circulatiy, William M. Klein
      • Re: SAME AS ('02 Standard) Clause - and circulatiy, Rick Smith
      • Re: SAME AS ('02 Standard) Clause - and circulatiy, William M. Klein
      • Re: SAME AS ('02 Standard) Clause - and circulatiy, Rick Smith
• "Free" workbench/IDE, MikeB
  • Re: "Free" workbench/IDE, William M. Klein
    • Re: "Free" workbench/IDE, MikeB
      • Re: "Free" workbench/IDE, Alistair
      • Re: "Free" workbench/IDE, Alistair
      • Re: "Free" workbench/IDE, William M. Klein
• Basement tinkerers and inventors, Graham Hobbs
  • Re: Basement tinkerers and inventors, Pete Dashwood
• Problems compiling Micro Focus COBOL program as GNT, sturk_25
  • Re: Problems compiling Micro Focus COBOL program as GNT, Simon Tobias
• COBOL Programmers Wanted in Columbia. Missouri, jobman
  • Re: COBOL Programmers Wanted in Columbia. Missouri, Frank Swarbrick
    • Re: COBOL Programmers Wanted in Columbia. Missouri,
      • Re: COBOL Programmers Wanted in Columbia. Missouri, SkippyPB
      • Re: COBOL Programmers Wanted in Columbia. Missouri,
• The pre-interview question..., HeyBub
  • Re: The pre-interview question..., LX-i
    • Re: The pre-interview question..., Pete Dashwood
      • Re: The pre-interview question..., Michael Mattias
      • Re: The pre-interview question...,
      • Re: The pre-interview question..., Michael Mattias
      • Re: The pre-interview question...,
      • Re: The pre-interview question..., klshafer@xxxxxxx
      • Re: The pre-interview question...,
      • Re: The pre-interview question..., Pete Dashwood
      • Re: The pre-interview question..., Michael Mattias
      • Re: The pre-interview question..., LX-i
  • Re: The pre-interview question..., Robert
  • Re: The pre-interview question..., Alistair
    • Re: The pre-interview question..., HeyBub
      • Re: The pre-interview question..., Alistair
  • Re: The pre-interview question..., Howard Brazee
    • Re: The pre-interview question..., Michael Mattias
• Bitmaps, jmoore207
  • Re: Bitmaps, jmoore207
    • Re: Bitmaps, Richard
      • Re: Bitmaps, tleaders...gmail.com
• How to send a Fax from Powercobol application ?, Massimo
  • Re: How to send a Fax from Powercobol application ?, HeyBub
  • Re: How to send a Fax from Powercobol application ?, Pete Dashwood
• Powercobol slow on Intel Core duo, Massimo
  • Re: Powercobol slow on Intel Core duo, Pete Dashwood
    • Re: Powercobol slow on Intel Core duo, Pete Dashwood
    • Re: Powercobol slow on Intel Core duo, Pete Dashwood
  • Re: Powercobol slow on Intel Core duo, Richard
• Urgent!!! Tandem-Base 24 Professionals for UAE, vam
  • Re: Urgent!!! Tandem-Base 24 Professionals for UAE,
• OT: ooRexx article and Mono atricle, Charles Hottel
• Re: MI5 Persecution: I am being ignored 17/4/97 (12474), tlmfru
  • Re: MI5 Persecution: I am being ignored 17/4/97 (12474),
    • Re: MI5 Persecution: I am being ignored 17/4/97 (12474), Frank Swarbrick
      • Re: MI5 Persecution: I am being ignored 17/4/97 (12474),
  • Re: MI5 Persecution: I am being ignored 17/4/97 (12474), LX-i
    • Re: MI5 Persecution: I am being ignored 17/4/97 (12474), tlmfru
• COPY code in procedure division was Re: Stop Run vs GoBack, Clark F Morris
• What's Hot?, Pete Dashwood
  • Re: What's Hot?, Pete Dashwood
• STICKY LINKAGE, Roger While
  • Re: STICKY LINKAGE, Frank Swarbrick
    • Re: STICKY LINKAGE, Sergey Kashyrin
      • Re: STICKY LINKAGE, Alistair
      • Re: STICKY LINKAGE, me
  • Re: STICKY LINKAGE, HeyBub
  • Re: STICKY LINKAGE, William M. Klein
    • Re: STICKY LINKAGE, Michael Mattias
    • Re: STICKY LINKAGE, Frank Swarbrick
      • Re: STICKY LINKAGE, William M. Klein
      • Re: STICKY LINKAGE, Frank Swarbrick
      • Re: STICKY LINKAGE, Sergey Kashyrin
      • Re: STICKY LINKAGE, Frank Swarbrick
      • Re: STICKY LINKAGE, Roger While
      • Re: STICKY LINKAGE, Frank Swarbrick
      • Re: STICKY LINKAGE, Robert
      • Re: STICKY LINKAGE, Roger While
      • Re: STICKY LINKAGE, Robert
      • Re: STICKY LINKAGE, William M. Klein
      • Re: STICKY LINKAGE, William M. Klein
      • Re: STICKY LINKAGE, Roger While
• Odd initializing code, Howard Brazee
  • Re: Odd initializing code, HeyBub
    • Re: Odd initializing code, LX-i
  • Re: Odd initializing code, Michael Mattias
    • Re: Odd initializing code, HeyBub
    • Re: Odd initializing code, Pete Dashwood
    • Re: Odd initializing code, HeyBub
• Urgent need for Cobol Developer, Sunny
  • Re: Urgent need for Cobol Developer, Alistair
  • Re: Urgent need for Cobol Developer,
• Mainframe Online Exam / Certification, Mainframe Group
• So here he goes again!, Frank Swarbrick
  • Re: So here he goes again!, Alistair
  • Re: So here he goes again!, William M. Klein
    • Re: So here he goes again!, Frank Swarbrick
• Regarding EVALUATE TRUE, klshafer@xxxxxxx
  • Re: Regarding EVALUATE TRUE, Alistair
    • Re: Regarding EVALUATE TRUE, Frank Swarbrick
      • Re: Regarding EVALUATE TRUE, LX-i
      • Re: Regarding EVALUATE TRUE, Alistair
    • Re: Regarding EVALUATE TRUE, Howard Brazee
      • Re: Regarding EVALUATE TRUE, John Reagan
  • Re: Regarding EVALUATE TRUE, me
    • Re: Regarding EVALUATE TRUE, Pete Dashwood
      • Re: Regarding EVALUATE TRUE, Frank Swarbrick
      • Re: Regarding EVALUATE TRUE, Doug Miller
      • Re: Regarding EVALUATE TRUE, Pete Dashwood
      • Re: Regarding EVALUATE TRUE, Doug Miller
  • Re: Regarding EVALUATE TRUE, Frank Swarbrick
    • Re: Regarding EVALUATE TRUE, klshafer@xxxxxxx
      • Re: Regarding EVALUATE TRUE, Frank Swarbrick
      • Re: Regarding EVALUATE TRUE, Richard
      • Re: Regarding EVALUATE TRUE, Frank Swarbrick
      • Re: Regarding EVALUATE TRUE, klshafer@xxxxxxx
      • Re: Regarding EVALUATE TRUE,
      • Re: Regarding EVALUATE TRUE, klshafer@xxxxxxx
      • Re: Regarding EVALUATE TRUE, Pete Dashwood
      • Re: Regarding EVALUATE TRUE, klshafer@xxxxxxx
      • Re: Regarding EVALUATE TRUE,
      • Re: Regarding EVALUATE TRUE, Charles Hottel
      • Re: Regarding EVALUATE TRUE, Pete Dashwood
      • Re: Regarding EVALUATE TRUE, Alistair
      • Re: Regarding EVALUATE TRUE, John Reagan
      • Re: Regarding EVALUATE TRUE, Pete Dashwood
      • Re: Regarding EVALUATE TRUE, HeyBub
      • Re: Regarding EVALUATE TRUE, John Reagan
      • Re: Regarding EVALUATE TRUE, Doug Miller
      • Re: Regarding EVALUATE TRUE, Pete Dashwood
      • Re: Regarding EVALUATE TRUE, Doug Miller
      • Re: Regarding EVALUATE TRUE, Pete Dashwood
      • Re: Regarding EVALUATE TRUE, Pete Dashwood
      • Re: Regarding EVALUATE TRUE, John Reagan
      • Re: Regarding EVALUATE TRUE, Pete Dashwood
      • Re: Regarding EVALUATE TRUE, klshafer@xxxxxxx
      • Re: Regarding EVALUATE TRUE, Pete Dashwood
      • Re: Regarding EVALUATE TRUE, Arnold Trembley
      • Re: Regarding EVALUATE TRUE, Doug Miller
      • Re: Regarding EVALUATE TRUE, Pete Dashwood
      • Re: Regarding EVALUATE TRUE, Doug Miller
      • Re: Regarding EVALUATE TRUE, Pete Dashwood
      • Re: Regarding EVALUATE TRUE, Doug Miller
      • Re: Regarding EVALUATE TRUE, klshafer@xxxxxxx
      • Re: Regarding EVALUATE TRUE, Pete Dashwood
      • Re: Regarding EVALUATE TRUE, Pete Dashwood
      • Re: Regarding EVALUATE TRUE,
      • Re: Regarding EVALUATE TRUE, Pete Dashwood
      • Re: Regarding EVALUATE TRUE, Howard Brazee
      • Re: Regarding EVALUATE TRUE, Howard Brazee
      • Re: Regarding EVALUATE TRUE, Doug Miller
      • Re: Regarding EVALUATE TRUE, Pete Dashwood
      • Re: Regarding EVALUATE TRUE, Howard Brazee
      • Re: Regarding EVALUATE TRUE, Frank Swarbrick
      • Re: Regarding EVALUATE TRUE, klshafer@xxxxxxx
      • Re: Regarding EVALUATE TRUE, Pete Dashwood
      • Re: Regarding EVALUATE TRUE, Howard Brazee
      • Re: Regarding EVALUATE TRUE, Pete Dashwood
      • Re: Regarding EVALUATE TRUE,
      • Re: Regarding EVALUATE TRUE, Pete Dashwood
      • Re: Regarding EVALUATE TRUE,
      • Re: Regarding EVALUATE TRUE, Pete Dashwood
      • Re: Regarding EVALUATE TRUE,
      • Re: Regarding EVALUATE TRUE, Pete Dashwood
      • Re: Regarding EVALUATE TRUE, Howard Brazee
      • Re: Regarding EVALUATE TRUE, Pete Dashwood
      • Re: Regarding EVALUATE TRUE, Howard Brazee
      • Re: Regarding EVALUATE TRUE, Pete Dashwood
      • OT: Re: Regarding EVALUATE TRUE, Roger While
      • Re: Regarding EVALUATE TRUE, Howard Brazee
      • Re: Regarding EVALUATE TRUE, Pete Dashwood
      • Re: Regarding EVALUATE TRUE,
      • Re: Regarding EVALUATE TRUE,
      • Re: Regarding EVALUATE TRUE, Frank Swarbrick
    • Re: Regarding EVALUATE TRUE,
      • Re: Regarding EVALUATE TRUE, LX-i
      • Re: Regarding EVALUATE TRUE,
      • Re: Regarding EVALUATE TRUE, klshafer@xxxxxxx
      • Re: Regarding EVALUATE TRUE, Howard Brazee
  • Re: Regarding EVALUATE TRUE,
  • Re: Regarding EVALUATE TRUE, LX-i
• evaluate false, again, Frank Swarbrick
  • Re: evaluate false, again, Doug Miller
  • Re: evaluate false, again, Alistair
    • Re: evaluate false, again, Pete Dashwood
      • Re: evaluate false, again, Alistair
    • Re: evaluate false, again, Howard Brazee
  • Re: evaluate false, again, Pete Dashwood
    • Re: evaluate false, again,
      • Re: evaluate false, again, Frank Swarbrick
      • Re: evaluate false, again, Doug Miller
      • Re: evaluate false, again, Frank Swarbrick
      • Re: evaluate false, again, Doug Miller
      • Re: evaluate false, again,
    • Re: evaluate false, again, William M. Klein
      • Re: evaluate false, again, Frank Swarbrick
      • Re: evaluate false, again, William M. Klein
      • Re: evaluate false, again, Frank Swarbrick
      • Re: evaluate false, again, Richard
      • Re: evaluate false, again, Howard Brazee
      • Re: evaluate false, again, Pete Dashwood
      • Message not available
      • Re: evaluate false, again, Pete Dashwood
      • Re: evaluate false, again, Pete Dashwood
      • Re: evaluate false, again, Michael Mattias
  • Re: evaluate false, again, HeyBub
    • Re: evaluate false, again, Pete Dashwood
      • Re: evaluate false, again, HeyBub
  • Re: evaluate false, again, LX-i
    • Re: evaluate false, again,
  • Re: evaluate false, again, Richard
    • Re: evaluate false, again, Frank Swarbrick
  • Re: evaluate false, again, Richard
    • Re: evaluate false, again, Frank Swarbrick
  • Re: evaluate false, again, SkippyPB
• COBOL/DB2 Date edit question, Graham Hobbs
  • Re: COBOL/DB2 Date edit question, Michael Mattias
  • Re: COBOL/DB2 Date edit question, Robert Jones
  • Re: COBOL/DB2 Date edit question, Pete Dashwood
    • Re: COBOL/DB2 Date edit question, Graham Hobbs
      • Re: COBOL/DB2 Date edit question, Pete Dashwood
      • Re: COBOL/DB2 Date edit question, Michael Mattias
      • Re: COBOL/DB2 Date edit question, Graham Hobbs
      • Re: COBOL/DB2 Date edit question, LX-i
      • Re: COBOL/DB2 Date edit question, Pete Dashwood
      • Re: COBOL/DB2 Date edit question, LX-i
      • Re: COBOL/DB2 Date edit question, Pete Dashwood
      • Re: COBOL/DB2 Date edit question, LX-i
      • field validation (was Re: COBOL/DB2 Date edit question), Frank Swarbrick
      • field validation (was Re: COBOL/DB2 Date edit question), Frank Swarbrick
      • Re: field validation (was Re: COBOL/DB2 Date edit question), Clark F Morris
      • Re: field validation (was Re: COBOL/DB2 Date edit question), Frank Swarbrick
      • Re: field validation (was Re: COBOL/DB2 Date edit question), Pete Dashwood
      • Re: field validation (was Re: COBOL/DB2 Date edit question),
      • Re: field validation (was Re: COBOL/DB2 Date edit question), Michael Mattias
      • Re: field validation (was Re: COBOL/DB2 Date edit question),
      • Re: field validation (was Re: COBOL/DB2 Date edit question), Frank Swarbrick
      • Re: field validation (was Re: COBOL/DB2 Date edit question), LX-i
      • Re: field validation (was Re: COBOL/DB2 Date edit question), Pete Dashwood
      • Re: field validation (was Re: COBOL/DB2 Date edit question), HeyBub
      • Re: field validation (was Re: COBOL/DB2 Date edit question), Binyamin Dissen
      • Re: field validation (was Re: COBOL/DB2 Date edit question), Howard Brazee
      • Re: field validation (was Re: COBOL/DB2 Date edit question), Pete Dashwood
      • Re: field validation (was Re: COBOL/DB2 Date edit question), Howard Brazee
      • Re: field validation (was Re: COBOL/DB2 Date edit question), Pete Dashwood
      • Re: field validation (was Re: COBOL/DB2 Date edit question), Clark F Morris
      • Re: field validation (was Re: COBOL/DB2 Date edit question), Howard Brazee
      • Re: field validation (was Re: COBOL/DB2 Date edit question), Pete Dashwood
      • Re: field validation (was Re: COBOL/DB2 Date edit question), Howard Brazee
      • Re: field validation (was Re: COBOL/DB2 Date edit question), Howard Brazee
      • Re: field validation (was Re: COBOL/DB2 Date edit question), Pete Dashwood
      • Re: field validation (was Re: COBOL/DB2 Date edit question), Howard Brazee
      • Browser standards was Re: field validation (was Re: COBOL/DB2 Date edit question), Clark F Morris
      • Re: Browser standards was Re: field validation (was Re: COBOL/DB2 Date edit question), Alistair
      • Re: field validation (was Re: COBOL/DB2 Date edit question), HeyBub
      • Re: field validation (was Re: COBOL/DB2 Date edit question), Pete Dashwood
      • Re: field validation (was Re: COBOL/DB2 Date edit question), Alistair
      • Re: field validation (was Re: COBOL/DB2 Date edit question), Pete Dashwood
      • Re: field validation (was Re: COBOL/DB2 Date edit question), Alistair
      • Re: field validation (was Re: COBOL/DB2 Date edit question), Pete Dashwood
      • Re: field validation (was Re: COBOL/DB2 Date edit question), HeyBub
      • Re: field validation (was Re: COBOL/DB2 Date edit question), LX-i
      • Re: field validation (was Re: COBOL/DB2 Date edit question), HeyBub
      • Re: field validation (was Re: COBOL/DB2 Date edit question), LX-i
      • Re: field validation (was Re: COBOL/DB2 Date edit question), LX-i
      • Re: field validation (was Re: COBOL/DB2 Date edit question), Richard
      • Re: field validation (was Re: COBOL/DB2 Date edit question), LX-i
      • Re: field validation (was Re: COBOL/DB2 Date edit question), Pete Dashwood
      • Re: field validation (was Re: COBOL/DB2 Date edit question), Howard Brazee
      • Re: field validation (was Re: COBOL/DB2 Date edit question), Pete Dashwood
      • Re: field validation (was Re: COBOL/DB2 Date edit question), Howard Brazee
      • Re: field validation (was Re: COBOL/DB2 Date edit question), Alistair
      • Re: field validation (was Re: COBOL/DB2 Date edit question), Howard Brazee
      • Re: field validation (was Re: COBOL/DB2 Date edit question), LX-i
      • Re: field validation (was Re: COBOL/DB2 Date edit question), Alistair
      • Re: field validation (was Re: COBOL/DB2 Date edit question),
      • Re: field validation (was Re: COBOL/DB2 Date edit question), Alistair
      • Re: field validation (was Re: COBOL/DB2 Date edit question),
      • Re: field validation (was Re: COBOL/DB2 Date edit question), Alistair
      • Re: field validation (was Re: COBOL/DB2 Date edit question),
      • Re: field validation (was Re: COBOL/DB2 Date edit question), Howard Brazee
      • Re: field validation (was Re: COBOL/DB2 Date edit question), Alistair
      • Re: field validation (was Re: COBOL/DB2 Date edit question),
      • Re: field validation (was Re: COBOL/DB2 Date edit question), LX-i
      • Re: field validation (was Re: COBOL/DB2 Date edit question), LX-i
      • Re: field validation (was Re: COBOL/DB2 Date edit question), Alistair
      • Re: field validation (was Re: COBOL/DB2 Date edit question), LX-i
      • Re: field validation (was Re: COBOL/DB2 Date edit question), Alistair
      • Re: field validation (was Re: COBOL/DB2 Date edit question), Clark F Morris
      • Re: field validation (was Re: COBOL/DB2 Date edit question), Alistair
      • Re: field validation (was Re: COBOL/DB2 Date edit question), Pete Dashwood
      • Re: field validation (was Re: COBOL/DB2 Date edit question), Howard Brazee
      • Re: field validation (was Re: COBOL/DB2 Date edit question), Pete Dashwood
      • Re: field validation (was Re: COBOL/DB2 Date edit question), Howard Brazee
      • Re: field validation (was Re: COBOL/DB2 Date edit question), HeyBub
      • Re: field validation (was Re: COBOL/DB2 Date edit question), Judson McClendon
      • Re: field validation (was Re: COBOL/DB2 Date edit question), Richard
      • Re: field validation (was Re: COBOL/DB2 Date edit question), Pete Dashwood
      • Re: field validation (was Re: COBOL/DB2 Date edit question), Alistair
      • Re: field validation (was Re: COBOL/DB2 Date edit question), Pete Dashwood
      • Re: field validation (was Re: COBOL/DB2 Date edit question), Richard
      • Re: field validation (was Re: COBOL/DB2 Date edit question), Howard Brazee
      • Re: field validation (was Re: COBOL/DB2 Date edit question), LX-i
      • Re: field validation (was Re: COBOL/DB2 Date edit question), LX-i
      • Re: COBOL/DB2 Date edit question, Pete Dashwood
      • Re: COBOL/DB2 Date edit question, Rick Smith
      • Re: COBOL/DB2 Date edit question, Pete Dashwood
      • Re: COBOL/DB2 Date edit question, Frank Swarbrick
      • Re: COBOL/DB2 Date edit question, Pete Dashwood
      • VisualAge COBOL (was: COBOL/DB2 Date edit question, William M. Klein
      • Re: VisualAge COBOL (was: COBOL/DB2 Date edit question, Pete Dashwood
      • Re: VisualAge COBOL (was: COBOL/DB2 Date edit question, Pete Dashwood
      • Re: VisualAge COBOL (was: COBOL/DB2 Date edit question, Richard
      • Re: VisualAge COBOL (was: COBOL/DB2 Date edit question, Pete Dashwood
• OT: Baby Update, Charles Hottel
  • Re: OT: Baby Update, Doug Miller
    • Re: OT: Baby Update, Charles Hottel
  • Re: OT: Baby Update,
  • Re: OT: Baby Update, SkippyPB
    • Re: OT: Baby Update, Charles Hottel
    • Re: OT: Baby Update, Charles Hottel
      • Re: OT: Baby Update, Paul Raulerson
  • Re: Baby Update, Pete Dashwood
  • Re: Baby Update, Pete Dashwood
    • Re: Baby Update, Charles Hottel
      • Re: Baby Update, Pete Dashwood
      • Re: Baby Update, Charles Hottel
  • Re: OT: Baby Update, LX-i
    • Re: OT: Baby Update, Charles Hottel
  • Re: OT: Baby Update, Howard Brazee
    • Re: OT: Baby Update, Charles Hottel
• Actual COBOL in Commodore 64, x01001x
  • Re: Actual COBOL in Commodore 64,
    • Re: Actual COBOL in Commodore 64, SkippyPB
  • Re: Actual COBOL in Commodore 64, Stephen W Boyd
    • Re: Actual COBOL in Commodore 64, SkippyPB
      • Re: Actual COBOL in Commodore 64, Stephen W Boyd
      • Re: Actual COBOL in Commodore 64, HeyBub
      • Re: Actual COBOL in Commodore 64, Pete Dashwood
      • Re: Actual COBOL in Commodore 64, HeyBub
      • Re: Actual COBOL in Commodore 64, Pete Dashwood
      • Re: Actual COBOL in Commodore 64, Richard Brady
      • Re: Actual COBOL in Commodore 64, Pete Dashwood
      • Re: Actual COBOL in Commodore 64, Robin Lee
      • Re: Actual COBOL in Commodore 64, SkippyPB
      • Re: Actual COBOL in Commodore 64, SkippyPB
      • Re: Actual COBOL in Commodore 64, Alistair
      • Re: Actual COBOL in Commodore 64, SkippyPB
      • Re: Actual COBOL in Commodore 64, Alistair
      • Re: Actual COBOL in Commodore 64, Alistair
• MicroFocus Dialog tutorial?, Paul H
  • Message not available
    • Re: MicroFocus Dialog tutorial?, Paul H
• Deleted records in Micro Focus Cobol, Dave Spencer
  • Re: Deleted records in Micro Focus Cobol, Richard
    • Re: Deleted records in Micro Focus Cobol, Dave Spencer
• COBOL subscript range checking, Frank Swarbrick
  • Re: COBOL subscript range checking, Robert Jones
  • Re: COBOL subscript range checking, Howard Brazee
  • Re: COBOL subscript range checking, Clark F Morris
    • Re: COBOL subscript range checking, Frank Swarbrick
  • Re: COBOL subscript range checking, LX-i
  • Re: COBOL subscript range checking, foodman123
    • Re: COBOL subscript range checking, HeyBub
    • Re: COBOL subscript range checking, Howard Brazee
    • Re: COBOL subscript range checking, Frank Swarbrick
      • Re: COBOL subscript range checking, Howard Brazee
      • Re: COBOL subscript range checking, Frank Swarbrick
      • Re: COBOL subscript range checking, Roger While
      • Re: COBOL subscript range checking, William M. Klein
      • Re: COBOL subscript range checking, Frank Swarbrick
      • Re: COBOL subscript range checking, Rick Smith
      • Re: COBOL subscript range checking, Howard Brazee
      • Re: COBOL subscript range checking, Frank Swarbrick
      • Re: COBOL subscript range checking, Rick Smith
      • Re: COBOL subscript range checking, Pete Dashwood
      • Re: COBOL subscript range checking, Clark F Morris
      • Re: COBOL subscript range checking, William M. Klein
      • Re: COBOL subscript range checking, Rick Smith
      • Re: COBOL subscript range checking, William M. Klein
      • Re: COBOL subscript range checking, William M. Klein
      • Re: COBOL subscript range checking, Rick Smith
      • Re: COBOL subscript range checking, William M. Klein
      • Re: COBOL subscript range checking, Rick Smith
      • Re: COBOL subscript range checking, William M. Klein
      • Re: COBOL subscript range checking, Rick Smith
      • Re: COBOL subscript range checking, William M. Klein
      • Re: COBOL subscript range checking, Rick Smith
      • "forward" references (was: COBOL subscript range checking, William M. Klein
      • Re: "forward" references (was: COBOL subscript range checking, Karl Kiesel
      • "forward" references (was: COBOL subscript range checking, William M. Klein
      • Re: "forward" references (was: COBOL subscript range checking, Rick Smith
      • Re: "forward" references (was: COBOL subscript range checking, William M. Klein
      • Re: "forward" references (was: COBOL subscript range checking, William M. Klein
      • Re: CONSTANT ENTRY (was "forward" references (was: COBOL subscript range checking)), Karl Kiesel
      • Re: CONSTANT ENTRY (was "forward" references (was: COBOL subscript range checking)), Roger While
      • Re: CONSTANT ENTRY (was "forward" references (was: COBOL subscript range checking)), Pete Dashwood
      • Re: CONSTANT ENTRY (was "forward" references (was: COBOL subscript range checking)), William M. Klein
      • Re: CONSTANT ENTRY (was "forward" references (was: COBOL subscript range checking)), Pete Dashwood
      • Re: CONSTANT ENTRY (was "forward" references (was: COBOL subscript range checking)), Rick Smith
      • Re: CONSTANT ENTRY (was "forward" references (was: COBOL subscript range checking)), William M. Klein
      • Re: CONSTANT ENTRY (was "forward" references (was: COBOL subscript range checking)), Pete Dashwood
      • Re: CONSTANT ENTRY (was "forward" references (was: COBOL subscript range checking)), Pete Dashwood
      • Message not available
      • Re: CONSTANT ENTRY (was "forward" references (was: COBOL subscript range checking)), Rick Smith
      • Re: CONSTANT ENTRY (was "forward" references (was: COBOL subscript range checking)), Pete Dashwood
      • Re: CONSTANT ENTRY (was "forward" references (was: COBOL subscript range checking)), William M. Klein
      • Re: CONSTANT ENTRY (was "forward" references (was: COBOL subscript range checking)), Karl Kiesel
      • Message not available
      • Re: CONSTANT ENTRY (was "forward" references (was: COBOL subscript range checking)), William M. Klein
      • Re: COBOL subscript range checking, Roger While
      • Re: COBOL subscript range checking, Alistair
      • Re: COBOL subscript range checking, Rick Smith
  • Re: COBOL subscript range checking, Andreas Lerch
  • Re: COBOL subscript range checking, CG
    • Re: COBOL subscript range checking, Howard Brazee
    • Re: COBOL subscript range checking, Howard Brazee
      • Re: COBOL subscript range checking, Binyamin Dissen
      • Re: COBOL subscript range checking,
      • Re: COBOL subscript range checking, HeyBub
      • Re: COBOL subscript range checking, Binyamin Dissen
      • Re: COBOL subscript range checking, Howard Brazee
    • Re: COBOL subscript range checking, Frank Swarbrick
  • Re: COBOL subscript range checking, William M. Klein
    • Re: COBOL subscript range checking, William M. Klein
• WAY (OT): What are we?, tlmfru
  • Re: WAY (OT): What are we?, Howard Brazee
  • Re: WAY (OT): What are we?, Pete Dashwood
  • Re: WAY (OT): What are we?, Jeff Campbell
  • Re: WAY (OT): What are we?, Frank Swarbrick
• Bank may need computer program, HeyBub
  • Re: Bank may need computer program, Sergey Kashyrin
  • Re: Bank may need computer program, Pete Dashwood
• pondering evaluate, Frank Swarbrick
  • Re: pondering evaluate,
  • Re: pondering evaluate, LX-i
  • Re: pondering evaluate, Rick Smith
    • Re: pondering evaluate, Zbikow
      • Re: pondering evaluate, Rick Smith
      • Re: pondering evaluate, Frank Swarbrick
    • Re: pondering evaluate, Frank Swarbrick
      • Re: pondering evaluate, Howard Brazee
      • Re: pondering evaluate, LX-i
      • Re: pondering evaluate, Frank Swarbrick
• COBOL in Commodore 64, x01001x
  • Re: COBOL in Commodore 64,
  • Re: COBOL in Commodore 64, SkippyPB
  • Re: COBOL in Commodore 64, Robert Jones
    • Re: COBOL in Commodore 64, Pete Dashwood
      • Re: COBOL in Commodore 64, Robert Jones
• Looking For Production Version of CobolScript, George McGinn
  • Re: Looking For Production Version of CobolScript, George McGinn
  • Re: Looking For Production Version of CobolScript, Alistair
• Ultimate efficiency using INITIALIZE statement in COBOL, ctolhurs
  • Re: Ultimate efficiency using INITIALIZE statement in COBOL, HeyBub
    • Re: Ultimate efficiency using INITIALIZE statement in COBOL, Pete Dashwood
      • Re: Ultimate efficiency using INITIALIZE statement in COBOL, HeyBub
      • Re: Ultimate efficiency using INITIALIZE statement in COBOL, Pete Dashwood
      • Re: Ultimate efficiency using INITIALIZE statement in COBOL, Judson McClendon
      • Re: Ultimate efficiency using INITIALIZE statement in COBOL, Alistair
      • Re: Ultimate efficiency using INITIALIZE statement in COBOL, Pete Dashwood
      • Re: Ultimate efficiency using INITIALIZE statement in COBOL, Sergey Kashyrin
      • Re: Ultimate efficiency using INITIALIZE statement in COBOL, Alistair
      • Re: Ultimate efficiency using INITIALIZE statement in COBOL, HeyBub
      • Re: Ultimate efficiency using INITIALIZE statement in COBOL, Alistair
      • Re: Ultimate efficiency using INITIALIZE statement in COBOL, Pete Dashwood
      • Re: Ultimate efficiency using INITIALIZE statement in COBOL, Pete Dashwood
      • Re: Ultimate efficiency using INITIALIZE statement in COBOL, Alistair
      • Re: Ultimate efficiency using INITIALIZE statement in COBOL, HeyBub
      • Re: Ultimate efficiency using INITIALIZE statement in COBOL, Howard Brazee
      • Re: Ultimate efficiency using INITIALIZE statement in COBOL, Alistair
      • Re: Ultimate efficiency using INITIALIZE statement in COBOL, HeyBub
      • Re: Ultimate efficiency using INITIALIZE statement in COBOL, Pete Dashwood
  • Re: Ultimate efficiency using INITIALIZE statement in COBOL, Pete Dashwood
  • Re: Ultimate efficiency using INITIALIZE statement in COBOL, Alistair
    • Re: Ultimate efficiency using INITIALIZE statement in COBOL, Pete Dashwood
      • Re: Ultimate efficiency using INITIALIZE statement in COBOL, Alistair
      • Re: Ultimate efficiency using INITIALIZE statement in COBOL, Pete Dashwood
      • Re: Ultimate efficiency using INITIALIZE statement in COBOL, Alistair
      • Re: Ultimate efficiency using INITIALIZE statement in COBOL, Pete Dashwood
      • Re: Ultimate efficiency using INITIALIZE statement in COBOL, Pete Dashwood
      • Re: Ultimate efficiency using INITIALIZE statement in COBOL, Alistair
      • Re: Ultimate efficiency using INITIALIZE statement in COBOL, Doug Miller
  • Re: Ultimate efficiency using INITIALIZE statement in COBOL, LX-i
    • Re: Ultimate efficiency using INITIALIZE statement in COBOL, Pete Dashwood
  • Re: Ultimate efficiency using INITIALIZE statement in COBOL, Robert Jones
  • Re: Ultimate efficiency using INITIALIZE statement in COBOL, Clark F Morris
    • Re: Ultimate efficiency using INITIALIZE statement in COBOL, Alistair
      • Re: Ultimate efficiency using INITIALIZE statement in COBOL, Clark F Morris
      • Re: Ultimate efficiency using INITIALIZE statement in COBOL, Pete Dashwood
  • Re: Ultimate efficiency using INITIALIZE statement in COBOL, George McGinn
    • Re: Ultimate efficiency using INITIALIZE statement in COBOL, Richard
      • Re: Ultimate efficiency using INITIALIZE statement in COBOL, Robert Jones
      • Re: Ultimate efficiency using INITIALIZE statement in COBOL, Robert Jones
    • Re: Ultimate efficiency using INITIALIZE statement in COBOL, Alistair
    • Re: Ultimate efficiency using INITIALIZE statement in COBOL, LX-i
• [OT] Laugh-Generating Situations,
  • Re: Laugh-Generating Situations, Alistair
    • Re: Laugh-Generating Situations,
      • Re: Laugh-Generating Situations, Alistair
      • Re: Laugh-Generating Situations,
      • Re: Laugh-Generating Situations, Pete Dashwood
      • Re: Laugh-Generating Situations, Alistair
  • Re: [OT] Laugh-Generating Situations, tlmfru
    • Re: Laugh-Generating Situations, Alistair
• nested programs, Frank Swarbrick
  • Re: nested programs, LX-i
  • Re: nested programs, Alistair
• MicroFocus .INT & .GNT, Paul H
  • Re: MicroFocus .INT & .GNT, Richard
  • Re: MicroFocus .INT & .GNT, Frank Swarbrick
    • Re: MicroFocus .INT & .GNT, Richard
• Re: MFCOBOL (Dos version), XP and COBLIB.DLE error message, ozzy . kopec
• Paagraphs and Sections, William M. Klein
  • Re: Paagraphs and Sections, Howard Brazee
    • Re: Paagraphs and Sections, Judson McClendon
  • Re: Paagraphs and Sections, Alistair
    • Re: Paagraphs and Sections, Pete Dashwood
    • Re: Paagraphs and Sections, Pete Dashwood
      • Re: Paagraphs and Sections, Alistair
• Baby Update, Charles Hottel
  • Re: Baby Update, Pete Dashwood
• COBOL Developer, coboltally
  • [OT] Interesting Housing Data (was Re: COBOL Developer),
• Position opening for Mainframe, smriti
  • Re: Position opening for Mainframe,
• Urgent requirement for Mainframe, smriti
  • Re: Urgent requirement for Mainframe,
  • Re: Urgent requirement for Mainframe, SkippyPB
    • Re: Urgent requirement for Mainframe,
      • Re: Urgent requirement for Mainframe, SkippyPB
      • Re: Urgent requirement for Mainframe,
  • <Possible follow-ups>
  • Urgent requirement for Mainframe, smriti
    • Re: Urgent requirement for Mainframe,
  • Urgent requirement for Mainframe, smriti
    • Re: Urgent requirement for Mainframe, Pete Dashwood
      • OT: fishy smells, Alistair
    • Re: Urgent requirement for Mainframe,
• Re: Tracing paragraph Names in Pro Cobol, balaji . amarnath
  • Re: Tracing paragraph Names in Pro Cobol,
    • Re: Tracing paragraph Names in Pro Cobol, balaji . amarnath
      • Re: Tracing paragraph Names in Pro Cobol, William M. Klein
      • Re: Tracing paragraph Names in Pro Cobol,
      • Re: Tracing paragraph Names in Pro Cobol, balaji . amarnath
      • Re: Tracing paragraph Names in Pro Cobol,
  • Re: Tracing paragraph Names in Pro Cobol, Richard
    • Re: Tracing paragraph Names in Pro Cobol, balaji . amarnath
    • Re: Tracing paragraph Names in Pro Cobol, Binyamin Dissen
• Re: ALTER design (Was: Code problems with Perform Thru Exit causes fallthrough), Arnold Trembley
  • Re: ALTER design (Was: Code problems with Perform Thru Exit causesfallthrough), tlmfru
  • <Possible follow-ups>
  • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fallthrough), Alistair
• Re: Code problems with Perform Thru Exit causes fall through, Rick Smith
  • Re: Code problems with Perform Thru Exit causes fall through, Doug Miller
    • Re: Code problems with Perform Thru Exit causes fall through, Rick Smith
      • Re: Code problems with Perform Thru Exit causes fall through, Doug Miller
      • Re: Code problems with Perform Thru Exit causes fall through, Pete Dashwood
      • Re: Code problems with Perform Thru Exit causes fall through, Richard
      • Re: Code problems with Perform Thru Exit causes fall through, Pete Dashwood
      • Re: Code problems with Perform Thru Exit causes fall through, Howard Brazee
      • Re: Code problems with Perform Thru Exit causes fall through, Pete Dashwood
  • Re: Code problems with Perform Thru Exit causes fall through, Richard
    • Re: Code problems with Perform Thru Exit causes fall through, Rick Smith
      • Re: Code problems with Perform Thru Exit causes fall through, Richard
      • Re: Code problems with Perform Thru Exit causes fall through, Rick Smith
      • Re: Code problems with Perform Thru Exit causes fall through, Richard
      • Re: Code problems with Perform Thru Exit causes fall through, Rick Smith
      • Re: Code problems with Perform Thru Exit causes fall through, Richard
      • Re: Code problems with Perform Thru Exit causes fall through, Rick Smith
      • Re: Code problems with Perform Thru Exit causes fall through, Richard
      • Re: Code problems with Perform Thru Exit causes fall through, Rick Smith
      • Re: Code problems with Perform Thru Exit causes fall through, Doug Miller
      • Re: Code problems with Perform Thru Exit causes fall through, Richard
      • Re: Code problems with Perform Thru Exit causes fall through, Rick Smith
      • Re: Code problems with Perform Thru Exit causes fall through, Rick Smith
      • Re: Code problems with Perform Thru Exit causes fall through, Richard
      • Re: Code problems with Perform Thru Exit causes fall through, Pete Dashwood
      • Re: Code problems with Perform Thru Exit causes fall through, Richard
      • Re: Code problems with Perform Thru Exit causes fall through, Pete Dashwood
      • Re: Code problems with Perform Thru Exit causes fall through, Clark F Morris
      • Re: Code problems with Perform Thru Exit causes fall through, Pete Dashwood
  • <Possible follow-ups>
  • Re: Code problems with Perform Thru Exit causes fall through, Doug Miller
  • Re: Code problems with Perform Thru Exit causes fall through, Rick Smith
    • Re: Code problems with Perform Thru Exit causes fall through, Doug Miller
      • Re: Code problems with Perform Thru Exit causes fall through, Rick Smith
      • Re: Code problems with Perform Thru Exit causes fall through, Richard
      • Re: Code problems with Perform Thru Exit causes fall through, Rick Smith
      • Re: Code problems with Perform Thru Exit causes fall through, Richard
      • Re: Code problems with Perform Thru Exit causes fall through, Rick Smith
  • Re: Code problems with Perform Thru Exit causes fall through, LX-i
    • Re: Code problems with Perform Thru Exit causes fall through, Doug Miller
    • Re: Code problems with Perform Thru Exit causes fall through,
    • Re: Code problems with Perform Thru Exit causes fall through, Howard Brazee
      • Re: Code problems with Perform Thru Exit causes fall through, Pete Dashwood
      • Re: Code problems with Perform Thru Exit causes fall through,
      • Re: Code problems with Perform Thru Exit causes fall through, Howard Brazee
      • Re: Code problems with Perform Thru Exit causes fall through, Alistair
      • Re: Code problems with Perform Thru Exit causes fall through, Pete Dashwood
      • OT: Daleks, Alistair
  • Re: Code problems with Perform Thru Exit causes fall through, Alistair
    • Re: Code problems with Perform Thru Exit causes fall through, Howard Brazee
  • Re: Code problems with Perform Thru Exit causes fall through, HeyBub
    • Re: Code problems with Perform Thru Exit causes fall through, Howard Brazee
      • Re: Code problems with Perform Thru Exit causes fall through, Pete Dashwood
    • Re: Code problems with Perform Thru Exit causes fall through, LX-i
    • Re: Code problems with Perform Thru Exit causes fall through, LX-i
    • Re: Code problems with Perform Thru Exit causes fall through, Pete Dashwood
      • Re: Code problems with Perform Thru Exit causes fall through, HeyBub
      • Re: Code problems with Perform Thru Exit causes fall through, Pete Dashwood
      • Re: Code problems with Perform Thru Exit causes fall through, Alistair
• Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Pete Dashwood
  • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Richard
    • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Pete Dashwood
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Howard Brazee
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Pete Dashwood
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through),
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Alistair
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through),
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), LX-i
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through),
      • OT: Kangaroo straights, Alistair
      • Re: OT: Kangaroo straights,
      • Re: OT: Kangaroo straights, Alistair
      • Re: OT: Kangaroo straights,
      • Re: OT: Kangaroo straights, Howard Brazee
      • Re: OT: Kangaroo straights, SkippyPB
      • Re: OT: Kangaroo straights,
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Alistair
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through),
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Alistair
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through),
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Howard Brazee
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Pete Dashwood
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Alistair
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Howard Brazee
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Pete Dashwood
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Binyamin Dissen
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through),
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Alistair
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through),
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through),
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Pete Dashwood
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Alistair
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Pete Dashwood
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Alistair
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Howard Brazee
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Doug Miller
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Pete Dashwood
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Doug Miller
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Pete Dashwood
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Alistair
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Pete Dashwood
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), donald tees
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Pete Dashwood
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through),
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Pete Dashwood
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Alistair
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through),
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Pete Dashwood
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through),
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Pete Dashwood
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through),
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Richard
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through),
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Pete Dashwood
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Howard Brazee
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Pete Dashwood
      • Security was Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Clark F Morris
      • Re: Security was Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Pete Dashwood
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), LX-i
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Doug Miller
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), LX-i
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Pete Dashwood
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Howard Brazee
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Pete Dashwood
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Alistair
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Pete Dashwood
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Alistair
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Richard
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Pete Dashwood
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Alistair
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Pete Dashwood
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through),
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Pete Dashwood
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through),
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Alistair
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through),
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Howard Brazee
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through),
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Howard Brazee
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through),
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Alistair
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Pete Dashwood
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Alistair
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through),
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Alistair
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through),
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Pete Dashwood
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Alistair
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Doug Miller
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), LX-i
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Doug Miller
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causesfall through), Frank Swarbrick
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Alistair
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Doug Miller
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Pete Dashwood
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Alistair
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Rick Smith
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Alistair
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Alistair
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Doug Miller
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Frank Swarbrick
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Alistair
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Howard Brazee
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Doug Miller
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Howard Brazee
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Frank Swarbrick
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Howard Brazee
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Doug Miller
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Howard Brazee
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Frank Swarbrick
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), LX-i
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causesfall through), Frank Swarbrick
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Howard Brazee
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Doug Miller
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Howard Brazee
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Doug Miller
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Richard
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Pete Dashwood
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Richard
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Pete Dashwood
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Richard
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through),
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Pete Dashwood
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through),
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Howard Brazee
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through),
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Pete Dashwood
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through),
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Pete Dashwood
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through),
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Pete Dashwood
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Alistair
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), tlmfru
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Pete Dashwood
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through),
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Alistair
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through),
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Alistair
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through),
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Pete Dashwood
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through),
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Pete Dashwood
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through),
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Pete Dashwood
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through),
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Alistair
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Pete Dashwood
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Alistair
    • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Howard Brazee
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Pete Dashwood
    • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), tlmfru
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Richard
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Pete Dashwood
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), tlmfru
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Pete Dashwood
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), tlmfru
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Howard Brazee
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Frank Swarbrick
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Doug Miller
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Frank Swarbrick
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through),
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Howard Brazee
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Richard
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Alistair
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), LX-i
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Alistair
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), LX-i
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Alistair
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), LX-i
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Richard
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Alistair
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Pete Dashwood
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Alistair
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), tlmfru
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Howard Brazee
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Frank Swarbrick
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Howard Brazee
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Pete Dashwood
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Pete Dashwood
  • <Possible follow-ups>
  • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Pete Dashwood
  • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Pete Dashwood
    • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through),
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Pete Dashwood
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through),
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Pete Dashwood
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through),
    • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Howard Brazee
  • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Alistair
  • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Binyamin Dissen
    • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Doug Miller
    • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Pete Dashwood
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), John Reagan
      • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through), Binyamin Dissen

We are proud to have Web Hosting and Rack Housing from 9 Net Avenue Deutschland.
(17)