By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
459,747 Members | 1,349 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 459,747 IT Pros & Developers. It's quick & easy.

Freeze Record after entry

P: n/a
Hi all, i am a beginner at this and would like to know if it is possible
to freeze a record on exit. In other words the user cannot go back and
change his record.

Les Stout

*** Sent via Developersdex http://www.developersdex.com ***
Nov 21 '05 #1
Share this Question
Share on Google+
6 Replies


P: n/a
"Les Stout" <an*******@devdex.com> wrote in message
news:3%**************@news.uswest.net...
Hi all, i am a beginner at this and would like to know if it is possible
to freeze a record on exit. In other words the user cannot go back and
change his record.


At form level, yes, by setting the form's "Allow Edits" property to "False".

HTH - Keith.
www.keithwilby.com
Nov 21 '05 #2

P: n/a
Hi Kieth, thanks but i need to do this automatically with code after the
user has made the entry and closed the form.

Les Stout

*** Sent via Developersdex http://www.developersdex.com ***
Nov 21 '05 #3

P: n/a
"Les Stout" <an*******@devdex.com> wrote in message
news:Wu**************@news.uswest.net...
Hi Kieth, thanks but i need to do this automatically with code after the
user has made the entry and closed the form.


This begs the question why. What will it achieve that the built in method
won't?
Nov 21 '05 #4

P: n/a
....it will allow it to be record-by-record.

Create a boolean field in the underlying table and default it to
Yes/True. In OnCurrent set allowEdits to the value of this field. In
OnAfterUpdate, set the value of that field and allowEdits to false.

Nov 21 '05 #5

P: n/a
"dc_it" <jc*******@gmail.com> wrote in message
news:11*********************@o13g2000cwo.googlegro ups.com...
...it will allow it to be record-by-record.

Create a boolean field in the underlying table and default it to
Yes/True. In OnCurrent set allowEdits to the value of this field. In
OnAfterUpdate, set the value of that field and allowEdits to false.

Maybe I'm missing something here. If you test for nulls in the Current event
then you have it record-by-record, no?
Nov 21 '05 #6

P: n/a
Yes, you could check for nulls for a new record and set allowEdits to
false in all other cases or you could attach it to the beforeInsert or
something. In any case, that won't allow for more varied behavior down
the road when the requirements inevitably change. I tend to err on the
side of slightly more complicated up front so life is easier next week.

Nov 21 '05 #7

This discussion thread is closed

Replies have been disabled for this discussion.