Hi All,
Thank you for the responses. The select record method, depending on our foundset size, can be fairly lengthly. I mean it is still usable, I was just wondering if there might be a faster way to achieve this.
Thomas:
I think duplicating a large foundset and then performing the find would end up taking longer than performing the selectRecord method. But I could give that a try.
goldcougar:
goldcougar wrote:Thats sort of an odd request. I've never needed to check if a PK was already loaded in the foundset, instead, if I want to load a record, I just use something like:
I thought this would be something that would sort of be basic functionality, didn't really consider this to be an odd request. The reason for this is that we have a search screen. The user will utilize the search and then move the items they want to another list. SImilar to functionality you would see in a lot of systems where a user can move single/multiple/all items back and forth between two lists. I have to check to see if an item exists in one list because I don't want the user to have duplicated values, and therefore I wouldn't add a new row to the dataset if it is a duplicate.
The select record method you have provide won't work in our situation because it is still doing the selectRecord. I can see this working for most cases, but because our foundset may be shared across a few other screens, which may have many related tabs, the select record may not be the most efficient method for us.
I hope that made sense...
mboegem:
I will try the custom query and see if that speeds things up a bit.
Thank you all again for the suggestions.