T
Tony
Hi All,
A couple of times I've 'redefined' reserved words such that I end up
corrupting my database (Access2K). For example, I set up a query and set a
field's name to 'DESCRIPTION'. From that point forward, Access thinks I'm
referring to the 'DESCRIPTION' as opposed to Description (as in MsgBox
Err.Desciption). I recover by going to my backup copy of my development
database and recreating anything that I've changed after confusing Access.
Does anyone know if, buried in the guts of the database, I can correct this
type of error? Perhaps in a system table?
Thanks,
Tony
A couple of times I've 'redefined' reserved words such that I end up
corrupting my database (Access2K). For example, I set up a query and set a
field's name to 'DESCRIPTION'. From that point forward, Access thinks I'm
referring to the 'DESCRIPTION' as opposed to Description (as in MsgBox
Err.Desciption). I recover by going to my backup copy of my development
database and recreating anything that I've changed after confusing Access.
Does anyone know if, buried in the guts of the database, I can correct this
type of error? Perhaps in a system table?
Thanks,
Tony