Take a look at Thread #533128.

>I have never built a table into an APP before. I have instead usually distributed tables such as MsgSvc as separate disk presences.
>
>We now have an application where we need to build tables into the application. We have no need to update the tables except at design time, and I don't want the users to be able to do so either.
>
>So we include the three tables (and their DBC) into the project, selecting INCLUDE in the Project Manager. Then we build.
>
>Weird behavior #1: After the build, but before we get control back, we get a series of error messages of the sort, "Variable 'FMF_cOptionName' not found." The identified "variable" is, in fact, one of the fields in one of our tables. We get several of these. No code is running at the time (or, at least, I can't see it in the Debug frame). Why are we getting these messages at build time? They don't show up in the Project Build errors list.
>
>Weird behavior #2: When we run the app, the first attempt to access the tables gives error 1542 ("Base table fields have been changed and no longer match view fields. View field properties cannot be set.") This is odd because the application is not using views - it uses the tables directly. I haven't yet been able to trap the line number (don't ask), and it runs fine in development mode.
>
>We have been able to run fine when the tables exist on disk. Just not built into the app. So is this truly weird behavior, or am I misunderstanding something about including data in an app?
>
>Thanks!
>zahid