A Microsoft Office (Excel, Word) forum. OfficeFrustration

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » OfficeFrustration forum » Microsoft Access » New Users
Site Map Home Register Authors List Search Today's Posts Mark Forums Read  

Text box help



 
 
Thread Tools Display Modes
  #21  
Old April 27th, 2005, 12:54 PM
BruceM
external usenet poster
 
Posts: n/a
Default

Ah, I see. The If...Then would be necessary only if DefaultValue is dropped
from the code. DefaultValue is redundant with If Me.NewRecord, or If...Then
is redundant with DefaultValue. But would DefaultValue apply any time the
field is blank, whether or not it is a new record, or only with a new record?
I think I remember something from earlier in the thread that the field in
question could be blank.

"Ken Snell [MVP]" wrote:

Your thought about carrying forward the value into new records is what I had
been understanding... but I'm not sure that this is what G.I.O. actually
wants?

A default value will be put into a record only when a new record is being
created. Thus, it should be unnecessary to use the If...Then test that you
suggest.

--

Ken Snell
MS ACCESS MVP

"BruceM" wrote in message
...
I've been watching this thread, and am going to pop in for a moment and
hope
that I don't muddy the waters. In a somewhat similar situation I had
something in the form's On Current event along the lines of:

If Me.NewRecord Then
Me.TheControlName.DefaultValue = """" & Me.TheControlName.Value & """"
End If

The middle part is, of course, the code Ken provided. I suppose this is
really more of a question for Ken than a suggestion that is ready to be
tried. As I understand it, you would want to carry the value forward only
when you are creating a new record.





  #22  
Old April 27th, 2005, 02:25 PM
Ken Snell [MVP]
external usenet poster
 
Posts: n/a
Default

An ACCESS form will insert the value from the Default Value property only at
the time of creating the new record. If you later delete the value from that
field, it will remain empty until you put something back into it
deliberately.

--

Ken Snell
MS ACCESS MVP

"BruceM" wrote in message
...
Ah, I see. The If...Then would be necessary only if DefaultValue is
dropped
from the code. DefaultValue is redundant with If Me.NewRecord, or
If...Then
is redundant with DefaultValue. But would DefaultValue apply any time the
field is blank, whether or not it is a new record, or only with a new
record?
I think I remember something from earlier in the thread that the field in
question could be blank.

"Ken Snell [MVP]" wrote:

Your thought about carrying forward the value into new records is what I
had
been understanding... but I'm not sure that this is what G.I.O. actually
wants?

A default value will be put into a record only when a new record is being
created. Thus, it should be unnecessary to use the If...Then test that
you
suggest.

--

Ken Snell
MS ACCESS MVP

"BruceM" wrote in message
...
I've been watching this thread, and am going to pop in for a moment and
hope
that I don't muddy the waters. In a somewhat similar situation I had
something in the form's On Current event along the lines of:

If Me.NewRecord Then
Me.TheControlName.DefaultValue = """" & Me.TheControlName.Value & """"
End If

The middle part is, of course, the code Ken provided. I suppose this
is
really more of a question for Ken than a suggestion that is ready to be
tried. As I understand it, you would want to carry the value forward
only
when you are creating a new record.







  #23  
Old April 27th, 2005, 11:15 PM
BruceM
external usenet poster
 
Posts: n/a
Default

Thanks. I realize now that I didn't quite understand default value.

"Ken Snell [MVP]" wrote:

An ACCESS form will insert the value from the Default Value property only at
the time of creating the new record. If you later delete the value from that
field, it will remain empty until you put something back into it
deliberately.

--

Ken Snell
MS ACCESS MVP

"BruceM" wrote in message
...
Ah, I see. The If...Then would be necessary only if DefaultValue is
dropped
from the code. DefaultValue is redundant with If Me.NewRecord, or
If...Then
is redundant with DefaultValue. But would DefaultValue apply any time the
field is blank, whether or not it is a new record, or only with a new
record?
I think I remember something from earlier in the thread that the field in
question could be blank.

"Ken Snell [MVP]" wrote:

Your thought about carrying forward the value into new records is what I
had
been understanding... but I'm not sure that this is what G.I.O. actually
wants?

A default value will be put into a record only when a new record is being
created. Thus, it should be unnecessary to use the If...Then test that
you
suggest.

--

Ken Snell
MS ACCESS MVP

"BruceM" wrote in message
...
I've been watching this thread, and am going to pop in for a moment and
hope
that I don't muddy the waters. In a somewhat similar situation I had
something in the form's On Current event along the lines of:

If Me.NewRecord Then
Me.TheControlName.DefaultValue = """" & Me.TheControlName.Value & """"
End If

The middle part is, of course, the code Ken provided. I suppose this
is
really more of a question for Ken than a suggestion that is ready to be
tried. As I understand it, you would want to carry the value forward
only
when you are creating a new record.








  #24  
Old April 28th, 2005, 03:29 PM
G.I.O.
external usenet poster
 
Posts: n/a
Default

Ken:

This is it! This will work for me just fine and dandy.

Thank you!
George

"Ken Snell [MVP]" wrote:


If you want to manually decide when to "copy" the value from one record
into another, use the Keyboard Shortcut key already existing in ACCESS --
namely, Ctrl + '. This will copy down the value from the previous record to
the current record for that field. Will that meet your needs?


 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Linking text boxes Volunteer Mom Publisher 7 November 12th, 2008 01:29 AM
Access reports with a horizontal line after each record??? Bill via AccessMonster.com Setting Up & Running Reports 6 March 9th, 2005 04:51 PM
Concatenatd fields in a query for a searching form Marc Running & Setting Up Queries 8 October 19th, 2004 08:49 PM
Too many hyperlinks? [email protected] Powerpoint 7 May 25th, 2004 02:19 AM
Vertical Text Orientation Paul Anderson [MSFT] Visio 0 May 11th, 2004 05:16 PM


All times are GMT +1. The time now is 11:46 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 OfficeFrustration.
The comments are property of their posters.