I trust some mates more familiar with distributed files will also respond...
but you might try this just to get you going: UniVerse handles things differently if you do OPEN '','CUST' TO FILENAME ELSE GOSUB DEALWITHIT SELECT FILENAME LOOP WHILE READNEXT more.stuff REPEAT or EXECUTE 'SSELECT CUST BY FIELD29 BY WHATEVER' CAPTURING SCREEN.IO CRT @SELECTED:" Custs to Service" LOOP .... I won't attempt to answer the internals of how these are handled by the kernal but the latter example lends itself more to debugging activity. In the first example you don't always have the entire selection 'at the ready', even in a non-distributed file system. -Baker -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Brenda Price Sent: Wednesday, September 13, 2006 10:17 AM To: [email protected] Subject: [U2] Debugging a program using distributed files causes core dump This is our first experience with distributed files. While debugging programs that have selected the whole file I get core dumps sometimes when I tell it to continue. As long as I am stepping through the program I am ok, as soon as I hit continue it blows up. I can take the debug statement out and run the programs without them blowing up. I've tracked back and found it is never on the same record when it blows. These files do have indices on them. We are stumped as to what is causing this behavior. This is not a critical error at this time because this is a conversion project. However, if this behavior continues after we are converted to this new method of business, it will be a big a problem the first time we have to get into the debugger to fix something during our critical processing and it blows up. Any idea's? On Universe 10.1.12, Reality flavor, Linux Advanced Server 3. Brenda Price Affiliated Acceptance Corporation ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
