On May 30, 10:38 am, RobUCSD <RobU...@discussions.microsoft.com>
wrote:
> In a table I have a fied named "fldCreator." On my form I have a txt box
> named txtCreator with the default value set to =CurrentUser(). It is not
> updating the the table. I can't figure out why. Any help would be greatly
> appreciated.
>
> Thanks, Rob
Is txtCreator bound to fldCreator? If not, this would prevent the
update. If you are trying to perform the update manually through code,
providing detailed code would help troubleshoot.
- GH
RobUCSD - 30 May 2007 16:34 GMT
Yes, the control is bound to fldCreator.
> On May 30, 10:38 am, RobUCSD <RobU...@discussions.microsoft.com>
> wrote:
[quoted text clipped - 10 lines]
>
> - GH
>In a table I have a fied named "fldCreator." On my form I have a txt box
>named txtCreator with the default value set to =CurrentUser(). It is not
>updating the the table. I can't figure out why. Any help would be greatly
>appreciated.
>
>Thanks, Rob
A control's default value property will apply only when the record is
"dirtied" by (manually) adding data to some other field on the form. Are you
doing so?
John W. Vinson [MVP]
RobUCSD - 30 May 2007 17:37 GMT
Yes. The wierd thing is is that when I'm on a new record I can see my
userName. But after I add to the record it goes away and doesn't add it to
the table. Thanks in advance for your continued assistance. Rob
> >In a table I have a fied named "fldCreator." On my form I have a txt box
> >named txtCreator with the default value set to =CurrentUser(). It is not
[quoted text clipped - 8 lines]
>
> John W. Vinson [MVP]
RobUCSD - 30 May 2007 17:40 GMT
Never Mind, I got it right now. Sorry for the inconvience and thanks for your
help. Rob
> Yes. The wierd thing is is that when I'm on a new record I can see my
> userName. But after I add to the record it goes away and doesn't add it to
[quoted text clipped - 12 lines]
> >
> > John W. Vinson [MVP]
Jeff Boyce - 30 May 2007 18:18 GMT
Consider posting the solution you found. Other folks visiting this
newsgroup might benefit from how you solved the issue...
Regards
Jeff Boyce
Microsoft Office/Access MVP
> Never Mind, I got it right now. Sorry for the inconvience and thanks for
> your
[quoted text clipped - 21 lines]
>> >
>> > John W. Vinson [MVP]
RobUCSD - 30 May 2007 18:26 GMT
It was just a dumb thing I was doing, not worth mentioning. Rob
> Consider posting the solution you found. Other folks visiting this
> newsgroup might benefit from how you solved the issue...
[quoted text clipped - 29 lines]
> >> >
> >> > John W. Vinson [MVP]