>No, VFP always checks inside the exe/app first. Btw, your solution sounds like a perfect description of how NOT to do things since a user can easily do anything with the data....! Have you ever heard of SQL injection?
>
>>I have an app that includes a reporting module; this runs "external" queries and reports - that is, they are not compiled into my app. So for example my reporting module might call c:\localQueries\query1.prg to generate a cursor and then c:\localReports\report1.frx to report on the data. If my compiled app also includes a prg called "query1", at run time this gets called in preference to the external query - despite me calling the external prg with a fully qualified path name. Is there some way to avoid this - other than making sure the external queries are all named differently to any prgs compiled into the app.
>>
>>Thanks in advance
>>Barry Sutton

Tore
Point taken - but the "users" are actually ME writing the query and report and dropping them into the external folders. I then put an entry into a reports table to point to the particular prg - only an administrator can access this table. It saves me having to compile a new app and distributing for every new query/report. I have just bought Stonefield Query SDK so hopefully that will help to an extent with this as it will run entirely separately from my app. (Not yet quite got my head around exactly how it all bolts together). I'm afraid I'm very much a part-time developer and sometimes I may not be doing things the way the professionals would do it.
Kind regards
Barry