Hi Christof,

Considering the circumstances, I'd have to agree that the issue is not trivial, though it may seem so before approaching it.
Yes, the easy access to internal resources in VFP is great most of the time, though it may create confusion when trying to access an explicit external resource (like path\file). Perhaps a setting (similar to ALLOWEXTERNAL) could have been applied to such cases, as well. Of course, it would be just a matter of discussion at this point.

>
>> such a trivial problem
>
>It's not really a trivial issue... Having to jump through hops in the special case of reading an external file with the same name as an included file is the price we pay for the totally transparent second file system that is built into VFP. Other languages make it harder to get at embedded resources and don't provide the same flexibility as VFP. In .NET, for instance, you can open resources as a Stream, but you can't treat them as a FileStream or a File.