Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Records mysteriously deleting in Visual Promatrix 6.0b
Message
From
22/10/2003 18:44:22
Hilmar Zonneveld
Independent Consultant
Cochabamba, Bolivia
 
 
To
17/10/2003 03:05:55
Gavin Reid
L & M Marketing Pty Ltd
Frenchs Forest, Australia
General information
Forum:
Visual FoxPro
Category:
Visual ProMatrix
Miscellaneous
Thread ID:
00839631
Message ID:
00841364
Views:
14
Well, I don't know Visual ProMatrix, but I can enumarate some ways a record can be deleted - it is then your task to find out where this fits into the framework.

  • A record can be deleted directly by the DELETE command.
  • A record, or a group of records, can be deleted by the DELETE FROM command (a SQL command).
  • A record, or a group of records, can be deleted through referential integrity, when you delete a record in another table.
  • Or, for that matter, with any delete trigger. (Ultimately, of course, both the RI and the delete trigger will use one of the first options I listed.)
  • When you delete a record in a view, the record in the underlying table should also be deleted. If the view's PK isn't defined correctly, you can easily delete too many records.

    For debugging, you may want to place a delete trigger into the table, which will intercept any attempt to delete a record. This function might eventually invoke SET STEP ON, for instance. Then, you can see the execution stack, and find out which methods, from which objects, tried to delete the record(s).

    HTH,

    Hilmar.


    >Hi All,
    >
    >I have a small application written in Visual Promatrix 6.0b and every now and then a record will be marked for deletion in a table even though the users don't have access to the delete functions. If I look in the audit trail I see no entry of the record being deleted. Nowhere in my code do I issue a delete. Can anyone think of a reason that a record would be deleted when the users don't have access to the delete functions? I am totally stumped as to why this is happening.
    >
    >The application runs in a number of locations on a mixture of W2K Terminal Servers and W2K Servers. All locations seem to be having the same problem.
    >
    >Any ideas?
    >
    >I've also posted this to the ProMatrix Newsgroups.
    >
    >Regards,
    >Gavin.
    Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
  • Previous
    Reply
    Map
    View

    Click here to load this message in the networking platform