>Kevin,
>
>Yes, I saw that. Here's a unique twist, the NEWID() stored procedure is NOT called when I run from development mode (and TRY to debug). It only runs when I create an APP or EXE file and execute them WITHOUT the development environment???? I did manage to track down that the error occurs on the "RETURN luID" line of code below (right near the end of NEWID()):
>
> IF EVAL(lcIDAlias+'.type') == 'C'
> RETURN TRIM(luID)
> ELSE
> RETURN luID
> ENDIF
>
>What would cause NEWID() to fire from an EXE but NOT fire from the development environment?
>
>Thanks!

It could be that the error handler is firing, which attempts to add a new entry to the error log. At some point (I forget the version), the errorlog was added to the DBC. It will throw an error if you haven't added an entry for it in the ID table.