forums.silverfrost.com

[KL]

Andy,

I misunderstood you, sorry!

I just repeated the test and got the same (wrong) result as before. Introducing iostat does not change the result. In my case, the error code is 0. How can this be?

I am using Windows XP but I do not believe, that such details are the reason.

Best regards,

Klaus

PS. I took the code from the forum, so I must have used the identical form as you.

[KL]

Andy, with the option status = 'new' the answer is correct, so I guess that something is strange with the option status = 'unknown'.

Klaus

[KL]

Dear Andy,
I suggest that we try to find out why the program gives different results
outside the forum. First we should exclude simple errors:
a) the directory 'd:\ftn95\tests\test41' must exist or the program must be modified.
b) the compiler options should be identical. I have noticed several times
that errors occur only for a specific option.

Klaus

PS When I tried to send this message directly to you I received an error message. Actually, I received this message yesterday more than once!

[PaulLaidler]

Klaus

Has this problem been resolved now?

If not can, you summarise the problem and I will try to find time to look at it on Friday.

[KL]

Dear Paul,

the status is as follows:

I have noticed an unexpected behaviour in the open statement and in the function fexists@:

1. Open statement: when I open a file in an existing directory, but I misspell the directory name and type a slash instead of a back-slash, the OPEN statement does not lead to an error. See the program which I have posted as the first one. Later on I found that the option status = 'new' gives in the test program (but not always!) the correct result, whereas status = 'unknown' failed. I used the OPEN statement to detect whether a directory exists.
2. "Sparge" recommended to use fexists@ instead of the open statement for finding out whether a directory exists. He did this applying fexist@ to a directory (which is actually not foreseen), you recommended to append the wild card '\*.*'. I have tried this and found that appending a wild card leads to an error message. See my second posted file.

May be that I have not applied fexists@ correctly. But I do not see that I am not using OPEN correctly. A look to the details of OPEN and fexists@ seems to be worthwhile.

Therefore, it would be nice if you could have another look to the problem. What did you mean when you indicated that "/" and "\" are sometimes used interchangably?

I consider this problem as not significant, nevertheless I would like to understand what happens.

Best regards

Klaus

[PaulLaidler]

Klaus

Here is my test program (C:\ftn95 already exists).

[KL]

Dear Paul,

thank you very much for your help. I could confirm your results but I will not continue in this direction. First, when I pass the misspelled directory name (slash instead of back-slash) as input path to "get_filtered_file@", this directory is not accepted. This is sometimes difficult to see since get_filtered_file@ stores a previous correct directory.

Secondly, I have severe difficulties in understanding fexists@, especially
I do not really understand the text. At least, it does not say that I can use fexists@ for the check of directories ("To search for a file with a given path name or wildcard"). When I append "\*.*" to a directory name (which you suggested in one of your mails), I get the error message 123. However, I must admit that I may have made another mistake.

Best regards and many thanks again
Klaus