prepare,declare,open,fetch:Need some clues

Items 6, 13, 22, 23 of my list seem somewhat appropriate today. Eschatological Laundry List 6. There is no way of getting all you want. 13. You don't really control anything. 22. Progress is an illusion. 23. Evil can be displaced but never eradicated, as all solutions breed new problems. By Shelly Kopp Author of GURU: Metaphors from a Pschotherapist Regarding my earlier postings with problems using prepare, declare, open, fetch , coding method I have found the thing that "breaks the bank" as it were. If I include this create table and drop table in my problem module then the program create temp table calc_method_set(lab_case_id integer, person_id integer, system char(8), relationship char(3)) . . . drop table calc_method_set will do one of two things when I execute it: 1. It will run completely and the "fetches" described in the earlier post will not retrieve what they are supposed to. or 2. Programs stops with the following error. . . SQL statement error number -245. Could not position within a file via an index. SYSTEM error number -103. ISAM error: illegal key descriptor (too many parts or too long). I have obviously hit some sort of limit. - There are a quite a few temp tables involved. - The executable is 3.6mg and includes probably hundreds of separately linked object files. - In addition it as the TCL interpreter linked in along with ESQL/C access routines to allow TCL to get data from SQL. To try and figure out what limit I am up against is some what of a problem. I need some clues? Thanks for taking the time to read this. -- Michael J. Kuhn Computer Systems Consultant phone:410-254-7060 Email: mkuhn@csd.clark.net, csd@clark.net mkuhn@rhlab.com c/o Baltimore Rh Typing Laboratory, Inc. phone:410-225-9595