Re: "Indexed or Primary Key cannot contain a Null value" / Autonum

Tech-Archive recommends: Fix windows errors by optimizing your registry

I comact/repair at least once per day, so that is not it.

a) It is bound to a query, but that query only draws from one table.
b) There are subforms, but they are all bound to different tables/queries.
c) No default values for either.

Any light you could shed on this would be most appreciated!
Kim M.

"Allen Browne" wrote:

Tom's suggestion to compact/repair the database is a good one.

If that doesn't solve it, tell us a bit more about this form. For example:

a) Is it a form bound to a query that uses multiple tables (in which case
Access may be trying to add a value to the other table -- particularly if
that table has any fields with a Default Value assigned.)

b) Is it a form with a subform that's bound to the same table (or a split
form since this seems to be A2007.)

c) Is there any Default Value in the text box for the autonumber field on
your form, or in the AutoNumber field if you open the table in design view?

--
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.


"Tom van Stiphout" <tom7744.no.spam@xxxxxxx> wrote in message
news:7des755bfbd1sg3jh3ubnijlfmju9m5hdk@xxxxxxxxxx
On Sat, 8 Aug 2009 14:55:01 -0700, Kim M.
<KimM@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

Did you compact the database; this behavior is quite unusual. The
autonumber is generated when the first character is entered in a new
record, whether the field is on the form or not.

-Tom.
Microsoft Access MVP


I keep getting this message whenever I try to enter a new record via a
form.
I click OK on the error message box, and then can continue without
problems.
But I'd still like to get rid of the message box.

What I THINK is happening is this: The primary key is an autonumber (and
does not appear on the form). I tried making it visible on the form to
experiment and this is what happens: It registers as "(new)", which I
guess
is a null value, until I click the OK on the error message box, at which
point it converts to an autonumber. So I guess my question is how do I
trigger the assignment of the autonumber WITHOUT having to go through that
pesky error message first?

(The program didn't always do this, but I am unable to pinpoint when it
started or what I did to bring it on.)

As always, thanks for your input!
Kim M.


.

Relevant Pages

  • Re: Resetting a field property from text to Autonumber in Access 2
    ... There does look like an extra square bracket in the error message you posted ... Also was not clear on where to put in "Autonumber". ... Everything went smoothly until I ran the query and got the following ... Change it to an Append query ...
    (microsoft.public.access.tablesdbdesign)
  • Re: Dear Microsoft: re: Error 3090...
    ... > When attempting to import a query as a table, ... > "Resultant table not allowed to have more than one AutoNumber field. ... The query you are importing has multiple Autonumber ...
    (microsoft.public.access.queries)
  • Autonumbering
    ... I wish to create through a query an autonumber column in a table, ... add an autonumber field to report I can see report with field that are ... I dont know how can I do this in a query. ...
    (microsoft.public.access.gettingstarted)
  • Re: put autonumber in another field
    ... I've used DMAX + 1 before to get a custom PK, but thought I had to use ... I'm using a RunningSum query to get a checkbook like result. ... RunningSum query looks to a autonumber field in the example I used ...
    (microsoft.public.access.queries)
  • Re: Coercing AutoNumber Value?
    ... Ran a query that appends to that table from a work table. ... tblIssuerRating's autonumber increment was messed up: ... My first question to you would be "why do you want to do this". ... you are trying to use this autonumber field for ANYTHING meaningful at ...
    (comp.databases.ms-access)