Hmm,

ON ERROR + RETRY


MartinaJ

>I will talk to the customer about AV (although they always say, "we do not have the AV"
>
>I used to have a problem with the application not connecting to the SQL Server. I solved it by creating a DO WHILE loop and trying to connect at least two times; then recover the connection (using Walter Meester's suggestion). This approach works very well.
>
>I wish I know how to call a function (in a FRX file) more than one time.
>
>
>>1. I don't know.
>>
>>2. WINAPI can tell you what process open a file.
>>
>>IMHO, faster is exclude FXP from AV checking list.
>>
>>MartinaJ
>>
>>>It is possible. Two follow up questions:
>>>1. How come other files are not blocked?
>>>2. Can I determine (in code) if it is AV?
>>>>Hi,
>>>>
>>>> Antivir block a frx file?
>>>>
>>>>MartinaJ
>>>>
>>>>>Hi,
>>>>>
>>>>>I believe I asked this question before; therefore, sorry for repeating.
>>>>>
>>>>>I see an error in a log file pointing to the application not being able to read an FRX file.
>>>>>Two things are strange (to me):
>>>>>1. The error has all the folders that are on MY computer. Example:
>>>>>

>>>>>Error reading file c:\users\dmitry\appdata\local\temp\myfuncts.fxp
>>>>>

>>>>>Apparently when the application is being built it stuffs the folder names from my PC. Can I prevent it?
>>>>>
>>>>>2. The Stack error log shows that the functions before the myfuncts.fxp fired. Otherwise, the error would happen on one of them. That is, the error (above) happens on Stack Level 9.
>>>>>All FRX files should be in the same EXE file. So, how come the application could read some functions but not the others?
>>>>>
>>>>>TIA