index or primary key cannot contain a null value

[Sandsnake]

Hiya

I am about to start a ropeless bungee jumping club, so any help would be super appreciated.

I am trying to create a new record entry form. It loads via a command button from a home form. Then when i try to save it, it tells me that the primary index cannot be null. I have essentially replicated a process i used earlier, but which is now not working at all. I have tried hiding the index, but to no avail. If i show it, it seems to require the user to enter the index number, which is bad (TM). I cannot seem to get the index to autonumber, any ideas? any details required will be provided, but not sure what to give.

Thanks for any help

EDIT:

When I launch the NEW_PATIENT_ENTRY form, it tells me that the record is not open, this might be the problem that the table is not being loaded. But unsure how to laod the table record. The form for new patient was created via the wizard using the PATIENT table as a base

[orange]

We need to see more info --- perhaps a table or a jpg of the table structure...

[Sandsnake]

We need to see more info --- perhaps a table or a jpg of the table structure...

Okay, I zipped and added the entire database.

[orange]

Not everyone has acc2007 or acc2010, so can not open the accdb.

[Sandsnake]

Not everyone has acc2007 or acc2010, so can not open the accdb.

So here is the table and the macro from the button that is giving me the grief

EDIT: and the relationships table too

[orange]

What are the data types of the ID fields? If these are autonumber, then Access will assign these automatically. Also, when using autonumber PK, be aware that numbers are NOT NECESSARILY contiguous. They may be, and usually are, but Access just ensures they are unique (not sequential). Also, when an autonumber is used, it is used and the next assignment will be a new number.

I don't have 2010 and I don't use Macros, so I'm not sure what the issue is. It is a fact that a Primary Key can not contain NULLs.

How did you create your form? Did you use a wizard to create a bound form?

[Sandsnake]

What are the data types of the ID fields? If these are autonumber, then Access will assign these automatically. Also, when using autonumber PK, be aware that numbers are NOT NECESSARILY contiguous. They may be, and usually are, but Access just ensures they are unique (not sequential). Also, when an autonumber is used, it is used and the next assignment will be a new number.

Am aware that contiguity is not implicit, that is not the issue.

I don't have 2010 and I don't use Macros, so I'm not sure what the issue is. It is a fact that a Primary Key can not contain NULLs.

This is obvious, the error message is simple to understand in meaning, it is just the specific reason that is elusive.

How did you create your form? Did you use a wizard to create a bound form?

Yes, i Used a wizard, not sure what the bound means tho?

TO clarify my original point, the error is not if 9 try to do a backend save on the table. That works. No problems. The error occurs when i try to save the form that is supposed to write to the table. I think the new patient form is not correctly loading the patient table.

[kimmer]

Your ID field in the PATIENT table is not an autonumber; you have it set as a double. Either change the data type to autonumber, or put a control for the ID field on the form so users can enter the value.

[Sandsnake]

Your ID field in the PATIENT table is not an autonumber; you have it set as a double. Either change the data type to autonumber, or put a control for the ID field on the form so users can enter the value.

Ah man!!!! it seems the way i carried the data across from the previous version changed the number types. okay, makes sense now, thank you

[Sandsnake]

Ok, so the problem was that when the tables got exported to Excel, they lost the value for the indices, so i fixed by recreating the db from scratch and altering the way the import was done by re-adding the indices new.

Now i still only have the problem that when i click on the add new patient form on the front page to add a new page, the button goes to the correct form, which has been created by wizard and is bound to the correct table, but it does not open the record.