Re: new record
- From: "Allen Browne" <AllenBrowne@xxxxxxxxxxxxxx>
- Date: Tue, 21 Feb 2006 09:25:30 +0800
The trick will be to identify what is causing the error, and address that.
For example, if yo have a text box bound to:
=DLookup("Field1", "Table1", "ID = " & [ID])
when you are at a new record, the ID field is probably Null. As a result,
the 3rd argument is just:
ID =
which is incomplete, and so generates an error. You solve that by using Nz()
to supply some value, e.g.:
=DLookup("Field1", "Table1", "ID = " & Nz([ID],0))
--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.
"dchristo" <dchristo@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:B2E03282-C014-4215-A08C-CF5D9413B557@xxxxxxxxxxxxxxxx
When I add a new record, most of my calculated fields are showing up as
#errors; however, if I add the minimal information to the record and close
the form. Once I reopend the form and go to the record all the
calculations
are correct.
How do I refresh the screen or what should I do so they I do not have to
close the form then reopen to continue inputting data into the record
.
- Prev by Date: Re: Entering Year as part of a macro
- Next by Date: Re: Unbound Combo Boxes - how to link into a report?
- Previous by thread: Re: Changing sort order
- Next by thread: Re: Access gets progressively slower in loading using CommandBar objec
- Index(es):
Relevant Pages
|
