Doru,

First of all, thanks for the reply. I think, Sergey's solution would be sufficient in our situation, but your ideas are also helpful. We're using Novell here, so could you please elaborate more on WhoHasWhat function? I asked similar question before, regarding determination of who has the file opened and I received several sites to check... I've downloaded software, but it didn't show me the necessary information, but gave couple of errors instead. Besides, I got some weird problems in GroupWise, etc., so I had to uninstall this software anyway...

Thanks again and thanks to Sergey, who I believe gave me the simplest solution. Since it's not my application, I'll pass this info to my colleague.

>Here is our "piece of logic":
>We put the names of the fxp/exe/app in a table, and use the value from there to load the procedure, or call EXEs, or APPs.
>If the current compiled procedure is myDBVal (in use by some users), then you compile to version 2, myDBVal2, and change the name in the table to myDBVal2. Usually, we go up to 3 or 4 and then cycle, with the version number.
>How do you know which fxp is in use - we have a WhoHasWhat function, but it only works on Novell and it is based on GPLIB. If you do not have a tool for that, you can probably assume that the version in use is what you have in the table and use the next number, i.e. do not reuse version number.
>
>
>>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.