|
Deb,
I tend to like inserting a default
row programmatically then editing that row on the form. This is mainly because
it makes a single version of the form a much more simple proposition. At least,
in v6.5 it did but in v7.1 that doesn't hold quite so true with all the property
commands.
Nevertheless, I still like that
method. I don't create a temp table, however, because the single row is all that
gets offered for editing - no next or previous rows, etc.
Yes, maybe there is an argument for
editing a bunch of rows but it's simple enough to get around - and that is
where you could utilise a temp table:
If you really need to,
create a temp table to hold the idnums of the rows you need to edit and
then edit where the idnum is in the temp table.
Security is a different problem. If
you don't want a user to change data then don't offer the opportunity. I use a
table in the database that knows the user's permissions and the menu system
doesn't display things that the user can't do. (Even for a single user like me
that makes me think before I make changes - well, most of the time it
does!)
Regards,
Alastair.
|
<<Glacier Bkgrd.jpg>>
