and if I replace "0" with the name of an open table - the same complaint! Yet as soon as I run the same command from the command window - no problemo...

Fortunately it only happens in one place in the code - the first line of a procedure. So it must reflect some bizarre memory problem presumably caused by something I've just run. Nothing obvious leaping out at me yet.

Anyone ever seen anything like it?

Harry