S
Steve
I'm using a user entered clientID number (as a text field
since it is not required for calculations) as the primary
Key in a tblClient. The tblClient and tblClientEvent are
set up in a one to many relationship using clientID as the
link. Forms frmClient and fsubClientEvent are linked by
the clientID number. I have written a code in the "on open
form" event that sets the ClientID default in
fsubClientEvent subform equal to the ClientID on the
frmClient parent form to keep the two forms synchronized.
In some instances, the clientID has zeros in the front.
When fsubClientEvent opens it truncates the zeros off the
front of the clientID number. Since it no longer matches
the true clientID an error message is generated, saying
there is no corresponding record in the tblClient table.
How can I prevent this from happening? Thanks
since it is not required for calculations) as the primary
Key in a tblClient. The tblClient and tblClientEvent are
set up in a one to many relationship using clientID as the
link. Forms frmClient and fsubClientEvent are linked by
the clientID number. I have written a code in the "on open
form" event that sets the ClientID default in
fsubClientEvent subform equal to the ClientID on the
frmClient parent form to keep the two forms synchronized.
In some instances, the clientID has zeros in the front.
When fsubClientEvent opens it truncates the zeros off the
front of the clientID number. Since it no longer matches
the true clientID an error message is generated, saying
there is no corresponding record in the tblClient table.
How can I prevent this from happening? Thanks