Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Exact and deleted recs - did everybody know this but me?
Message
From
25/07/2006 13:10:31
Mike Yearwood
Toronto, Ontario, Canada
 
 
To
25/07/2006 12:39:32
Dragan Nedeljkovich (Online)
Now officially retired
Zrenjanin, Serbia
General information
Forum:
Visual FoxPro
Category:
Coding, syntax & commands
Miscellaneous
Thread ID:
01139176
Message ID:
01139804
Views:
7
>>>Thanks for the suggestion. So, the above then becomes:
>>>
>>>
SELECT id, UPPER(firstname), UPPER(lastname), DELETED() as deletedrec ;
>>>FROM tablename INTO CURSOR crsTemp
>>>And it works.
>>>
>>It will only work as long as you select from only one table. The minute you join in another table, it will fail to work again.
>
>This is easily circumvented by selecting from this particular table into a temp cursor, then use that in any joins later.

Quite right!

>
>Funny though, I had this idea to have ...deleted() as ... yesterday, but had an impression that someone already said that :). Comes with long threads.

Naomi first and then Thomas, I think and even Tore and me.

I take it farthest though. A single t/f flag is seldom sufficient. A datetime is the ultimate. You get several extra abilities. A few are: 1, you can see all the records a malicious person deleted in one day - without a complex audit trail. 2 - You can delete records more than one year old and then pack. .T./.F. you can't decide which records to physically delete. 3 - You can recall records deleted in the last 10 minutes.
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform