Hello All, It looks like everybody is using the first byte of the record as the space holder for storing record number. Being a byte, it can hold at most 127 records. Is that going to be a problem? Ofcourse i know that sun validaters are not going to put that many records. Just wondering if its going to be a drawback to the design?
You dont need to save record no. You can find the record number logically. The start of ist record shows first record after the end of ist record (i think 183 bytes) its the 2nd record and so on.
Yeah that's the way I'm doing it - it wouldn't be robust enough if the client had to implement modify/create/remove functionality because you'd need something to uniquely identify each record...but I think it's good enough for the specification.
The thing is though, as you going to display the record number to the user?
I'm having problems retrieving the record number from the JTable (when a user selects to book a record) if I hide the record number column, so the only way I can figure it out is to show the record number to the user.
Has anyone else had problems like this?
Chris
Post by:autobot
Oh the stink of it! Smell my tiny ad!
a bit of art, as a gift, the permaculture playing cards
![[Logo]](/templates/default/mobile/images/mobile-moose.gif)
