Multiple User Access Warnings - Unsure if problem is fundamental

[ArviLaanemets]

Btw, I think you must have some Primary Key in your Main Client Database table - in case it is not a composite Primary Key, it essentially must be ProjectID.

It is possible, that you have several projects (simultaneously, or distributed in time) for same customer. When this is the case, then you must have separate fields e.g. ProjectID and CustomerID (simply having customer name in table allows typos when entering the name), and notes must be probably linked to ProjectID, not to ClientID.

[ArviLaanemets]

Btw, I think you must have some Primary Key in your Main Client Database table - in case it is not a composite Primary Key, it essentially must be ProjectID.

It is possible, that you have several projects (simultaneously, or distributed in time) for same customer. When this is the case, then you must have separate fields e.g. ProjectID and CustomerID (simply having customer name in table allows typos when entering the name), and notes must be probably linked to ProjectID, not to CustomerID.

We basically enter every single piece of info on the client in the table titled "Main Client Database".

This will work until you have a single row for client. When you have several rows for client, you have to enter the same info again for every row - without any typos! And Access will not assist you in avoiding those typos.
With separate client registry, you enter the client info once. and whenever the client info changes sometimes, you update the client info, and it is available for all entries where CustomerID is stored (of-course when you need the some customer info at entry time to be saved and remain unchanged in future, then you have to store this info as value instead of CustomerID).

[Steveoh421]

Yes, we have a primary key in the Main Client Database so every time we enter a record for a client it has it's own unique number. I understand what you mean with reference to manually entering data without typos, although I don't think that is our main issue.

We enter the client info initially in the Main Client Database table. The Client File form is in place as it filters the relevant information from the Main Client Database whenever we need quick info on a file. So if one of our employees receives a phone call from a client, we just search for their record using the Client File form and we can see all the relevant info, plus we have the benefit of seeing the notes which are detailed in the "Customer History Notes".

The two main issues we have are that we get these errors and warnings when we load up the database (regardless of whether its being accessed by a single user, or multiple users) and the second issue is that some of the client records have become randomly corrupt, specifically in relation to the "Customer History Notes" which is a particular problem if we've collated several notes over a few weeks/months.