Values carried over from one record to the next

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Adam - Regus - 31 Jan 2006 20:55 GMT

I hope that I explain this in a manner that makes sense.
On the form that I am working on, I have a box that I've setup to input

the amount of scans that I've done for a client (call it the SCANS
box) and in the next box I've made it automatically input the cost of
the scans. All seems well with the formula in the cost box, but for
some reason, when i go to the next record the value stays in the SCANS
box instead of starting out blank, like I want it to.

As a newbie, I appreciate all your help!

Thanks,
Adam

Reply to this Message

salad - 31 Jan 2006 21:05 GMT

> I hope that I explain this in a manner that makes sense.
> On the form that I am working on, I have a box that I've setup to input
[quoted text clipped - 9 lines]
> Thanks,
> Adam

In the OnCurrent event of the form you could put in a Requery line.
Me.CalculatedTextBoxName.Requery

Reply to this Message

Jeremy Wallace - 31 Jan 2006 21:05 GMT

Sounds like Scans is unbound. If so, add code to the Current event of
the form that does this:
me!Scans = ""

Jeremy
--
Jeremy Wallace
Fund for the City of New York

Reply to this Message

Adam - Regus - 31 Jan 2006 21:27 GMT

The box is indeed unbound. Dumb question, but is it possible just to
bind the box to something? If I put in SCAN in the control source, I
just get a #name? error. I guess I made the box wrong. Once again, I
thank you for your time and patience. I seriously dont know much about
access. ;) (my boss should be paying someone to do this...)

Thanks,
Adam

Reply to this Message

Tim Marshall - 31 Jan 2006 22:05 GMT

> The box is indeed unbound. Dumb question, but is it possible just to
> bind the box to something? If I put in SCAN in the control source, I
> just get a #name? error.

There are two possibilities for this error that come to mind right away.

The first: do you have a query as the form's recordsource that has a
field in it called SCAN? If not, the #Name error is Access asking
"Where in the blazes do I get 'SCAN' from, huh?" 8)

The second: if you do have a field name in the form's underlying query
called SCAN, then check the name property of your text box in question.
It is probably called "SCAN" as well. If so, what you've done is name
the text box "SCAN" and also told Acces that the controlsource of the
text box is "SCAN". Once again, this will get Access angry at you. To
correct this, rename the name property of the textbox to something like
"txtScan", ie, something different from the controlsource.

Signature

Tim http://www.ucs.mun.ca/~tmarshal/
^o<
/#) "Burp-beep, burp-beep, burp-beep?" - Quaker Jake
/^^ "Whatcha doin?" - Ditto "TIM-MAY!!" - Me

Reply to this Message