Splitting Database - Index or primary key cannot contain a Null value

[Tizzy22]

Hi All, I hope you can help.



I've inherited a rather messy database which and I need to split it in order for us all to be able to enter data at the same time without problems however I get the following message:

Index or primary key cannot contain a Null value

It happens at the table that contains the majority of the data (typical) but I cannot understand what could be causing it. I've check Null Primary Key field and removed all of the "required" statuses out of the fields but still no luck.

I tested on a backup database from a couple of days ago and it worked. Only difference is I've added a few bits and bobs since then and 1 field in the table it's stalling on but this field doesn't contain any null values either and I've tried deleting that field in my test database but made no difference.

I'm tearing my hair out now - is there any easy way to check what it's actually referring to??

Thanks in advance,

Tizzy

[RuralGuy]

It throws the error when you use the build-in splitter, right?

[Tizzy22]

Yeah its the built in one . I deleted all the data from my table in test and it split fine so I'm 100% sure now it's that table but can't understand why.

[RuralGuy]

Will your db do a Compact and Repair?

[Tizzy22]

Hi RG,

Compact and repair works fine.

[RuralGuy]

Well I'm not sure what is causing the issue but it is pretty easy to manually split a db. Do you want to just do that?

[Tizzy22]

Hi RG, sorry for the delay in responding and thanks so much for your help so far.

Yes if it's easy enough to do then that would be great. Can you tell me how though??

[RuralGuy]

I would create two new db's named ~FE.accdb and ~BE.accdb using your name for the "~". Then open the BE and *import* the tables from your original file. Save and close and open the FE. Import everything BUT the tables from the original file. Use the Linked Table Manager to add in the linked tables from the BE. Save and close and your done. Test it to see if it works.

[Tizzy22]

Hi RG, I posted an update yesterday but it doesnt seem to have appeared! I found instructions on how to do it manually and tried - it imported every table apart from the one I'm having problems with.

So this morning I've tried again. This time I imported everything I could then exported the PEOPLE (the one I have problems with) table to Excel and imported it to the back end letting access recreate the primary key.

I'm now getting loads of VB errors. I probably should've mentioned the database also allows me to track who has logged on and when and who inputted each record. I think maybe I need these tables in the front end in order for it to work properly. I think I'll have to give this up for the time being but at least I've managed to split it

Thanks for your help!!

[RuralGuy]

Okay. Thanks for the update. Post back here if you need further assistance.