C
Cathy C
Update: This week I've been checking out the possibility of bad data. We
found several such records, corrected them, but same problem. I tried adding
a product in the subform to a record and it worked. The data entry operator
tried it and it crashed it. I noticed that I had used a start up date of
12/1/04 and she had used 1/5/05 for hers. This made me check out the
properties of the field. Although the sign up date was indexed (duplicates
OK), the start up date was not. So, I indexed it and it worked fine with a
2004 or 2005 date. She then realized that the problem started at about the
time she started adding records that had a 2005 start up date. I thought the
problem was solved until she added a totally new record (the others were
just new products for an existing record) and it crashed again. I thought
maybe indexing the LASTTRAN field in the main form might solve the problem,
but it didn't.
Any ideas why these 2005 dates in the subform were crashing the program?
Thanks,
Cathy
found several such records, corrected them, but same problem. I tried adding
a product in the subform to a record and it worked. The data entry operator
tried it and it crashed it. I noticed that I had used a start up date of
12/1/04 and she had used 1/5/05 for hers. This made me check out the
properties of the field. Although the sign up date was indexed (duplicates
OK), the start up date was not. So, I indexed it and it worked fine with a
2004 or 2005 date. She then realized that the problem started at about the
time she started adding records that had a 2005 start up date. I thought the
problem was solved until she added a totally new record (the others were
just new products for an existing record) and it crashed again. I thought
maybe indexing the LASTTRAN field in the main form might solve the problem,
but it didn't.
Any ideas why these 2005 dates in the subform were crashing the program?
Thanks,
Cathy