Karen,
I have never done this (I think) and am not sure if it is possible,
however can a person abort the delete function from within a before
delete trigger?
If you can, you could ask for a password and continue the delete. If
the password is not given or is incorrect, abort the delete pr
Doug: That's how I started out. Altho I never abbreviate and always use
"DELETE ROWS" I figured I couldn't use that for a search in case I for some
reason abbreviated or did "DELETE FROM".
So I searched for "FROM claim" because I would never split that into separate
lines of code (darn those
What about using FIND in Custom EEPS, Expressions and Control Properties
in all forms for:
DEL ROWS FROM [tablename]
DELETE ROWS FROM [tablename]
DEL FROM [tablename]
DELETE FROM [tablename]
If you R:Style or use consistent coding you might skip some of the above
commands.
And possibly RMD fi
Well it might take a little work, but this is what I would do.
#1 - I would lock the table down with access control as tight as
practically possible.
Add a single character field to the table to use as a Delete Flag (hangover
from the old DBase days, using an asterisk (0x2A) as the marker or
Adrian: That's what I'm thinking some kind of "system" user without a name.
Nope, database is not accessed by any other program (client is very small,
simple, very non-tech). This is the only trigger in the database. Deletions
are contiguous. Looking at the time of deletion, they all follow
5 matches
Mail list logo