> Its part of a wizard that the user can cancel from. On reentry and
> running code again, I get an error that states that the <name of gdb>
> already exists. This is on scrIBExport.Execute command found while
> tracing and after erasing that particular file on the HD. It just is not
> there at all. After the error, I do note a 0 byte file of the same name.
> BTW, as long as I only run this wizard once during a app session,
> everything works fine.

You can preface the create database statement with a drop database statement
to ensure it is removed if it exists.
You can also use the SET IGNOREEXCEPTCNT (?) to tell it to ignore an
exception if it isn't there to drop.

HTH,
Jason Wharton
CPS - Mesa AZ
http://www.ibobjects.com