Why don't you just store the record index somewhere (eg a hidden array)
when you ran the query and pass it back to delete?
DmQueryNextInCategory() passes back the index as one
of its paremeters. Is this how you are retrieving your
records?
-Ken
> ----------
> From: Michael S. Davis[SMTP:[EMAIL PROTECTED]]
> Reply To: [EMAIL PROTECTED]
> Sent: Tuesday, December 21, 1999 10:56 AM
> To: [EMAIL PROTECTED]
> Subject: Still no answer - Index of Selected item in Category
>
>
> I still need a solution to this problem. I want to be able
> to delete a record that is displayed in a list that is displayed
> on a form. The list contains items within a category.
>
> So there might be 4 items in the list because there are only
> 4 items within a specific category.
>
> When I select item 3, for instance, I want to delete that item
> from the database. But I need the index, within the database, to do
> that. And the index might be 100, or 30 or who knows what.
>
> The only function that I see that is close is DmPositionInCategory() but
> that appears to return the position in the list (3 in this case) and
> not the index within the database, that is needed by DmDeleteRecord().
>
> Can someone explain how to get the index, needed by DmDeleteRecord()
> when I have a subset of the database, by using a category.
>
>
> Thanks
>
>
>
