Ed, Thanks for your reply.

Lets see if I have this right :-

One option is to have different Config.fpw files and use command line switch:

So for my FPW app , I start as : MyFPW.exe -CMyFPW
For my VFP app , I start as : MyVFP.exe -cMyVFP ( Where MyFPW and MyVFP are copies of Config.Fpw)

Then in MyFPW file I have a line with : Resource = 'MyFPW.Dbf'
in MyVFP file I have a line with : Resource = 'MyVFP.DBF'

where MyFPW.dbf and MyVFP.dbf are copies of Foxuser.dbf


Just one other q. Is the Foxuser.dbf required and what does it hold ?

Regards

Gerard










>>Hi.
>>I am getting this message up , from a folder , where I hve two apps running, one from FPW 2.6 and one from VFP 6.
>>
>>I remember that a solution is to use a command line switch and a resource setting but am unclear as to exactly where to put these.
>>( Is it Config.fpw or Foxuser ???? and what to do with them)
>
>The problem is that they share a common FOXUSER (the resource file); you can fix this by having different CONFIG files for each product; the control coming from either the command line switches or by embedding the CONFIG.FPW in the compiled VFP app.
>
>Another alternative, which is a bit neater, is to include RESOURCE=OFF in the comon CONFIG.FPW, and then have each app select a resource file during it's initialization, assuming that you use things contained in the resource file. There's no rule stating that the resource file must be named FOXUSER.DBF; you could have two mutually-exclusinve FOXUSER files, one named FOXU2_6.DBF, and the other named FOXU6_0.DBF, and have your app SET RESOURCE TO the appropriate file during startup.