>If I set my project to INCLUDE my DBC that I define my remote SQL views, will the EXE created use THAT included DBC before it would use another DBC that is local on the production machine?
>
>So when I create my EXE of my project, it should compile in the DBC
>
>Then I copy the EXE to a production drive. If by chance there was also a DBC with the same name already on the production drive, will that cause a problem, or will it use the compiled in DBC no matter what?
>
>Obviously the disadvantage of an included DBC is you can not modify it, but this is all for remote views to SQL 2000 and any ercord or data change will only be in that SQL table/tables

Joel,

You can include that DBC in your project to be compiled into the exe. At runtime, VFP will use the DBC inside the exe. Unless (and this is untested) you specifically path out to an existing DBC on disk. One of the benefits of compiling a "views-only" DBC is that you don't have to worry about record locking contentions with multiple users trying to requery the same views at the same time. And you don't have to send out local copies of the DBC to get those results.

HTH,
Chad