|
Yeah, well, it seems that SQL won't do it again. When I STRSQL and do the same steps, now it just reads through the records once like I would expect. I did change the refresh to *FORWARD after I tested so now it's even faster. I don't think I'll ever know why this did it. Maybe I'll submit it to Unsolved Mysteries <g> Thanks, Jim Langston From: thomas@inorbit.com Jim: On Wed, 13 March 2002, Jim Langston wrote: > This I would expect from two files. The only thing was, I had only one f= ile > I was selecting from. The exact SQL statement I used was: > SELECT * FROM INP95 WHERE URID95 =3D 'PRISM ' I'd expect that no good answer can come until the list first sees a file de= scription of INP95. An answer might be obvious from there or questions migh= t be suggested from it. I can think of various ways that SQL statement coul= d result in the messages you saw. Tom Liotta
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.