>>From the documentation:
>>
>>"Issue SET RESOURCE TO without a resource file name to open the default Foxuser.dbf resource file. Issuing SET RESOURCE TO performs an implicit SET RESOURCE ON."
>
>George, thank you for reply.
>
>Look carefully to the last two lines:
>
>SET RESOURCE TO
>
>sets the resource to some foxuser file.
>
>In this case, previous resource file (ressurss.dbf) table must be released and can be used by USE command or by any other application.
>
>However last line
>
>USE RESSURSS causes error. This means that when RESSURSS.DBF is
>used as resource file,
>
>SET RESOURCE TO
>
>COMMAND DOES NOT RELEASE RESSURSS.DBF file.
>
>This is related to the ressurss.fpt file structure. This
>fpt file confuces VFP 7 so that it does not release it after SET RESOURCE TO
>command.
>
>THIS IS BUG !

First, I do not appreciate your shouting at me and, therefore, may be a little more blunt and a little less tactful than usual.

In order for this to be a bug it must be replicatable with any valid resource file

It is not! I've tested the following over and over and have not been able to replicate it. My normal resource file is differently named than the default. The code below which I've used to do these tests has not once demonstrated the behavior you describe.

lcresource = SET("Resource" , 1)
* lcresource equals C:\FOX\VFPUSER.DBF
USE (lcresource) AGAIN IN 0 ALIAS myresource
USE
SET RESOURCE TO
* The following prints C:\WINNT\SYSTEM32\FOXUSER.DBF
? SET("Resource" , 1)
USE C:\FOX\VFPUSER.DBF
USE
SET RESOURCE TO (lcresource)

I have done this both with and without using the resource file again.

It is to no one's advantage to start yelling "BUG!" without being able to categorically prove and replicate it. In fact, it does a disservice to the community as a whole. The mere fact that it cannot be replicated with any valid resource file dis-proves your statement.

SET BUG OFF