>>>>I have an old FPD2.6 system, using old tables.
>>>>
>>>>I'm piecemeal replacing the old system with a new VFP system, replacing functionality as and when it's needed. e.g. the users have created and/or amended data with the old system, and is using my new functionality to make any new-style changes, and report on the data.
>>>>
>>>>When they enter my new app they get the message like "Do you want to replace the old resource file with a new (VFP)?", to which I've instructed them to say "no".
>>>>
>>>>However, there's always the chance, when, say, typing ahead, that they'll say "yes". So 2 questions:
>>>>
>>>>1. Is it that important if they say "yes"? I imagine that, when they subsequently go into the DOS system they'll get like an "alien resource file" message.
>>>>
>>>>2. Their use of the new system doesn't seem to be impaired by saying "no" so is there a mechanism to get round this question dialog, i.e not have the system asking if they want to replace?
>>>>
>>>>I don't want to set reso off if I can help it.
>>>>
>>>>'ppreciate it
>>>>
>>>>Terry
>>>
>>>What you have in Resource File?
>>>You could try to do something like, if you use RESOURCE file in your application (I don't) :
>>>put
>>>

>>>RESOURCE=OFF in Config.fpw
>>>*** in your main program put
>>>SET RESOURCE TO VFPResDbf.DBF
>>>SET RESOURCE ON
>>>

>>>
>>>Keep n mind that this is not tested at all.
>>
>>Hi BB
>>
>>Thanks.
>>
>>I assume you mean FOXUSER.DBF - Oh, the usual stuff: audit of what's taken place, positions of windows etc. Interestingly, the "old" res. file has included some of the "new" actions, like calls to my new report, ect.
>>
>>So it seems that FPD is happy to record the modern action, only in the old-style table.
>>
>>Is your code above telling the VFP app to use the VFP Foxuser, after setting reso off? Then presumably the old system hjust looks for its own? I think I get the drift. Hmmm, but as the user has been instructed NOT to create a new reso file, I assume there isn't one to switch to.
>
>
>I don't know , but if FPD uses a different name as resource you didn't get this message, didn't you? That is why I suggest to use a different name in VFP.
>Yes in the code above I tell VFP to use new resource file and then set it to ON. You could check to see if you have that file in application folder and if it doesn't exists create it:
>

>*** in your main program put
>lcNewRes = ADDBS(JUSTPATH(SYS(16,1)))+[VFPResDbf.DBF]
>IF EMPTY(SYS(2000,lcNewRes))
>   CREATE TABLE (lcNewRes) FREE (Type C(12), ID C(12), Name M, ReadOnly L, CkVal N(6,0), Data M, Updated D)
>ENDIF
>SET RESOURCE TO (lcNewRes)
>SET RESOURCE ON
>

Thanks a lot, old chum. BTW The name of resource file for FPD has always been just FOXUSER.DBF hasn't it.