Quick and dirty solution: Try to delete that .fxp and then check if it still exists. If the deletion was succesfull you can compile it.
>Hi everybody,
>
>We have the following piece of logic: we keep all database validation methods in a table, then if any validation method was changed, we re-create a procedure file with all methods in it (using textmerge) and then re-compile this file. Quite often, however, we got an error, that .fxp file could not be created (if somebody is using the application at this time). My question is: can we prevent this error and how, and if not, how can we trap it?
>
>Thanks in advance.
--sb--