Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » ElevateDB Technical Support » Support Forums » ElevateDB General Discussion » View Thread |
Messages 1 to 4 of 4 total |
Position after deleting rows |
Sun, May 7 2017 9:38 AM | Permanent Link |
Roy Lambert NLH Associates Team Elevate | I'm altering some code in my email subsystem to speed up deleting rows (think spam or just junk). If I delete just one row I generally try and place the cursor on the next row down, or the last row if the it was the last row deleted. When deleting a selection I have mixed views on the best position - top, bottom, before the first item in the selection, after the last item or what.
Just interested in what others do. Roy Lambert |
Sun, May 7 2017 6:23 PM | Permanent Link |
Raul Team Elevate | On 5/7/2017 9:38 AM, Roy Lambert wrote:
> Just interested in what others do. We're doing same thing you're doing - selecting next item. For multi-select it's the next existing item after whatever user selected last as part of multi-select. So actual position depends on how they selected. Raul |
Mon, May 8 2017 3:44 AM | Permanent Link |
Matthew Jones | Roy Lambert wrote:
> I'm altering some code in my email subsystem to speed up deleting rows (think spam or just junk). If I delete just one row I generally try and place the cursor on the next row down, or the last row if the it was the last row deleted. When deleting a selection I have mixed views on the best position - top, bottom, before the first item in the selection, after the last item or what. First, why would anyone delete any email? Well, apart from spam. But I think it sort of depends on the order you are showing them in, and what process someone is doing it. If you have newer to the top, and select going up, then I'd expect to be on the "next" one. That way the process works better. Thinking further, I really like the way Virtual Access works - you simply mark a particular message as deleted, and it doesn't actually go until you refresh. And it hasn't actually been deleted yet, so you can show deleted messages. Only when you purge does it actually get removed from the database. We haven't deleted anything other than spam for nearly twenty years. -- Matthew Jones |
Mon, May 8 2017 5:18 AM | Permanent Link |
Roy Lambert NLH Associates Team Elevate | Matthew
>First, why would anyone delete any email? Well, apart from spam. We also get a wadge of news feeds - FT, elReg amongst others as they come in they're dumped in an unread news folder and when everyone's read them (or I get fed up) they are deleted. >But I think it sort of depends on the order you are showing them in, and what process someone is doing it. If you have newer to the top, and select going up, then I'd expect to be on the "next" one. That way the process works better. > >Thinking further, I really like the way Virtual Access works - you simply mark a particular message as deleted, and it doesn't actually go until you refresh. And it hasn't actually been deleted yet, so you can show deleted messages. Only when you purge does it actually get removed from the database. > >We haven't deleted anything other than spam for nearly twenty years. Ah yes - the magpie approach - I use it with modifications. My system (recruitment) has two files - ELN (Emails, Letters, Notes) and Emails if an email is received from a known contact it arrives in emails and after its been read is transfered to ELN linked to the contact. I have ELN entries going back to 1994 and Email entries back to 2005. Unsolicited cvs generally stay in Emails. Entries in ELN generally stay until the contact is deleted. Entries in Emails go when they are no longer commercially or intellectually of interest. Roy |
This web page was last updated on Tuesday, September 17, 2024 at 04:19 AM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |