=?Utf-8?B?Q1c=?= wrote in
:

Bob, thanks for your suggestions...yes, all other controls on the
form are editable, it's just those that have their Default Value
set to DLookup that are giving the trouble. And yes, the Allow
Edits property is set to Yes. And no, I'm not using a query as the
source for the form, it's based directly upon the CostsActual
table. I wonder if you have any further thoughts...?
Many thanks
CW

First, test to see if removing the default value lets you edit those
controls. If removal allows editing, try a static value in the
default value.

if it is the dlookup causing the problem a workaround is to set the
values using some code in thte before insert event of the form.


"Bob Quintal" wrote:

=?Utf-8?B?Q1c=?= wrote in
:

Many thanks for your prompt reply...yes I do have the Control
Sources set, they point to the relevant fields in the
CostsActual table. That's cos the way I want it to work, users
will initially (by default) see the quoted amounts which are
being pulled from the Quotes table. But if the actual amounts
have come in different, they need to input those and have them
stored in the CostsActual table. In this way, we can work out
variances between amounts allowed for within our quotes (stored
in the Quotes table and not overwritten) and the actual cost
amounts (newly stored in the CostsActual table).
Hope this clarifies what I'm trying to do, and why. The
question now is, HOW ?!
Thanks again
CW

Are other fields in the form editable? The form itself can be
locked, by setting the allow_edits property to No.

Are you perhaps using a query to reference the table to the form.
Some queries are read only, If it's a query, can you edit the
data directly in the query?



"Linq Adams via AccessMonster.com" wrote:

A Default Value can be overwritten by manually entering new
data, so you shouldn't be having a problem. On the other hand,
setting the Control Source to something, like a value
retrieved using DLookup(), cannot be overwritten. First thing
I'd do is look at the Control Source and make sure you didn't
place something there during the development process and
forget to remove it.

Is the form updatable, i.e. can you enter and save other data?

Other than that, based on the facts you've given, I'd have to
lean towards corruption of some sort.

--
There's ALWAYS more than one way to skin a cat!

Answers/posts based on Access 2000/2003

Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/Forums.aspx/access-
forms/200804/1






--
Bob Quintal

PA is y I've altered my email address.
** Posted from http://www.teranews.com **





--
Bob Quintal

PA is y I've altered my email address.
** Posted from http://www.teranews.com **