Ok... Maybe I'm a tad slow... (Lack of sleep and not enough coffee...)
You said that the problem only occurs with your one result set. When you say that you're getting the data from a spreadsheet, how are you reading it in? Are you trying to access the raw XLS dataset? Or did you export the data as a .csv file? I don't believe it's a bug because of the fact that it only occurs in one data set, and that you could be introducing an error in a couple of places. (The data set itself for example.)(load program) So what am I missing? > -----Original Message----- > From: news [mailto:[EMAIL PROTECTED] On Behalf Of tom > Sent: Wednesday, March 01, 2006 5:01 AM > To: [email protected] > Subject: Re: order by > > > > There still something is wrong. I recreated the database without > composite index, imported 1200 records without error, viewed > them and the programm was hanging at record 1100 without messages, > I killed the process after waiting 5 minutes and restarted > derby network server. I created a composite index and viewed the > data, now the sorting problem that I described at the beginning of this > thread appears again. pooh >
