Data Not Saving from Subform to Table

I have 2 coworkers who enter data that, for no apparent reason, doesn't save.
Here is what I have:
-I have a master back and 3 separate front ends. Everything is linked
through the ClientID in the tblMainClientInfo, and is showing as correctly
linked on all computers
-When 2 coworkers enter in case notes in subfrmCaseNts, they claim it looks
fine, but when they navigate back to that client later, the case note has
disappeared (and checking tblCaseNts where it should be saved shows no such
record existing).
-The subform is linked to the main form via ClientID
-This problem existed when multiple people were in the same front end at the
same time, so I gave the coworkers their own front ends with a brand new,
uncorrupted subfrmCaseNts
-The main form already has a me.dirty command upon closing

The problem continues even after I installed the individualized front ends.
This only seems to happen to 2 coworkers and I can't discern a pattern of
time of day or particular client. tblCaseNts gets entries from other people
and they don't seem to have problems with it (entering it in to the original
shared front end the 2 coworkers were using, or one of the other 2 front
ends). Entire months of case notes by these two coworkers are disappearing
and I'm not sure what else to look for. I'm not sure if it is their
particular machines or if it's something systemic. Everything is linked
correctly as far as I can tell. All entries in tblCaseNts are date stamped
upon creation and other notes will be saved just fine while on the same day
the 2 coworkers will have issues. Is there a way I can prevent case notes
from being deleted from the table? Is there another link between the subform
and the table I need to check? Any help is greatly appreciated.

multiple people in the same front end is not supported. even though it works
fine 90% of the time...it does cause quirky inexplicable problems.

so you need a front end per user as a starting point to get further support
on this issue.

if the records are truly not there - then you should double check your
me.dirty

if the records are there but not re-displaying with the correct parent
record then your issue would be the cross referencing field.



"mewins" wrote:

I have 2 coworkers who enter data that, for no apparent reason, doesn't save.
Here is what I have:
-I have a master back and 3 separate front ends. Everything is linked
through the ClientID in the tblMainClientInfo, and is showing as correctly
linked on all computers
-When 2 coworkers enter in case notes in subfrmCaseNts, they claim it looks
fine, but when they navigate back to that client later, the case note has
disappeared (and checking tblCaseNts where it should be saved shows no such
record existing).
-The subform is linked to the main form via ClientID
-This problem existed when multiple people were in the same front end at the
same time, so I gave the coworkers their own front ends with a brand new,
uncorrupted subfrmCaseNts
-The main form already has a me.dirty command upon closing

The problem continues even after I installed the individualized front ends.
This only seems to happen to 2 coworkers and I can't discern a pattern of
time of day or particular client. tblCaseNts gets entries from other people
and they don't seem to have problems with it (entering it in to the original
shared front end the 2 coworkers were using, or one of the other 2 front
ends). Entire months of case notes by these two coworkers are disappearing
and I'm not sure what else to look for. I'm not sure if it is their
particular machines or if it's something systemic. Everything is linked
correctly as far as I can tell. All entries in tblCaseNts are date stamped
upon creation and other notes will be saved just fine while on the same day
the 2 coworkers will have issues. Is there a way I can prevent case notes
from being deleted from the table? Is there another link between the subform
and the table I need to check? Any help is greatly appreciated.

I know the multiple front ends can cause problems, so for the 2 coworkers I
made individual front ends for them to use but the problem of data not saving
is still happening. I have checked the tblCaseNts to see if some records
have saved but without ClientIDs (and a select few have), but none that match
up with the 20 clients who have multiple case notes per client that have
completely disappeared. To exit the main form, I have a command button that
I made with the wizard, coding below:

Private Sub Command102_Click()
On Error GoTo Err_Command102_Click

If Me.Dirty Then
Me.Dirty = False
End If

DoCmd.Close


Exit_Command102_Click:
Exit Sub

Err_Command102_Click:
MsgBox Err.Description
Resume Exit_Command102_Click

End Sub


Is there a problem with the me.dirty coding? The other issue is that out of
roughly 8 people entering in case notes on a daily bases this data problem is
only with 2 coworkers. Is there something on their actual computers I should
be looking for?

Thanks for any advice.

"GBA" wrote:

multiple people in the same front end is not supported. even though it works
fine 90% of the time...it does cause quirky inexplicable problems.

so you need a front end per user as a starting point to get further support
on this issue.

if the records are truly not there - then you should double check your
me.dirty

if the records are there but not re-displaying with the correct parent
record then your issue would be the cross referencing field.

well I think you need to first rule out the me.dirty. your code is fine.
you should sanity check by putting a couple characters into a field...do not
tab out...and close that form...and then go direct to the table and see if
those characters are in the table.

me.dirty is not going to explain multiple records gone missing - unless they
were never there in the first place.

if you are saying that there were records definitely there - and now these
records are gone - - you have some other issue. Access does not delete
records - never - unless a delete query occurs or someone types over the data.

so you have to isolate this issue to whether or not the data is really going
in ......or whether it is data that is/was definitely there and is not
re-appearing.

subform data that does not reappear does not mean that the data has
disappeared. it is still in the table - but not being cross referenced to
the parent record and thus not appearing in the subform.

once again; data that was in a table - never disappears - unless there has
been a delete record event or it is written over.

if you don't want to take the time to trouble shoot this then consider
changing tactics: as you say only 2 pcs have this problem; delete their
front end and copy a front end from one of the working pcs....

"mewins" wrote:

I know the multiple front ends can cause problems, so for the 2 coworkers I
made individual front ends for them to use but the problem of data not saving
is still happening. I have checked the tblCaseNts to see if some records
have saved but without ClientIDs (and a select few have), but none that match
up with the 20 clients who have multiple case notes per client that have
completely disappeared. To exit the main form, I have a command button that
I made with the wizard, coding below:

Private Sub Command102_Click()
On Error GoTo Err_Command102_Click

If Me.Dirty Then
Me.Dirty = False
End If

DoCmd.Close


Exit_Command102_Click:
Exit Sub

Err_Command102_Click:
MsgBox Err.Description
Resume Exit_Command102_Click

End Sub


Is there a problem with the me.dirty coding? The other issue is that out of
roughly 8 people entering in case notes on a daily bases this data problem is
only with 2 coworkers. Is there something on their actual computers I should
be looking for?

Thanks for any advice.

"GBA" wrote:

multiple people in the same front end is not supported. even though it works
fine 90% of the time...it does cause quirky inexplicable problems.

so you need a front end per user as a starting point to get further support
on this issue.

if the records are truly not there - then you should double check your
me.dirty

if the records are there but not re-displaying with the correct parent
record then your issue would be the cross referencing field.