I ran into a situation where I entered an invalid default value expression for a field in the table designer. It was the name of a .prg with is not valid. I wrote a stored procedure for the default value and went back to the table designer and backspaced the prg filename and replaced it with a call to the stored procedure. Now when I add a record, it tries to execute the prg which no longer exists. When I click OK on the error dialog it goes ahead and calls the stored procedure and opens a record with the correct default value.
How do I stop the database from trying to execute the prg which was
the first (incorrect) expression I entered?

Thanx,

Eric Kleeman Idaho