Primary Key can not contain a null value

[Bruce]

I am far from an expert w/Access 2003 but I have managed to create a database. I use forms to add data to tables. The main form is Orders where I enter an OrderID. I use a command button to launch the next form where I add WorkOrders associated with the OrderID. I set up the


WorkOrders form to pull the OrderID from the main form and populate that
field. The workorders table primary key is a field called SID which I fill in
manually (at this stage, later to be autonumber). After filling in all data in the WorkOrders form and hit "enter" or install a "Save" command button Access comes back with "Primary key can not contain a null value", when obviously the PK value is not null.

I'm doing all of this with no knowledge of VB code, just using wizzards and modifying properties. Any basic help is appreciated.

[RuralGuy]

Why is this field not an AutoNumber field now? What are you waiting for?

[ConneXionLost]

Hi Bruce,

Check to ensure your main "Orders" form has saved the record (and created the OrderID) before you launch the next form.

Cheers,

[rwp289]

Start with the basics:

Are you sure that the textbox that you are entering the SID (your Workorders PK) is actual bound to SID field in the Workorders table?

[RuralGuy]

I think the OP has gone on vacation.

[Bruce]

Sorry, forgot to come back after finding the answer. I was binding the text field to the value on another open form instead of using VB to set the value of the field. Once I bound the text field to the table and coded the value to equal (on load) the value of the textbox on the other form, it worked.

Learning more as time passes. Thanks!

[RuralGuy]

Great! Thanks for the update.