Hi All,



 I'm a long time listener (learner) to the group but first time poster.   I

have learned a lot from the group and sure appreciate the tips and great

advice!!



 I have a ~10 user multi-user Access 2000 application in which the database

resides on an NT server and reports/screens/etc, reside on client PC's.



Every now and then we get a "#Deleted" value in a memo field in an

employee's record.   When that happens, a compact and repair will correct

the problem, but while that flag is in the field, it confuses both a Visual

Basic program which accessess those records and causes Access itself to act

crazy when you 'touch' one of the affected records in table sheet edit mode.

How does this happen and how could I guard against it?



Also, does anyone know a way to prevent an Access form from allowing nulls

into a field element??   Occasionally, we also get null values into certain

fields and it also will cause the VB program to 'flip out'.  I'm sure they

are 'sneaking in' from the use of some Access data entry screens, but I'm

unsure

what the user is typing to put the flag into the field or how to prevent it

from happening...





Thanks a lot,

Howard Henderson