>I read something here about putting the DBC in the exe to avoid corruption.
>Is it a good habit ? I suppose that, then, it becomes impossible to modify the structure of the database ? Is there any other bad side of this ?
>
>Thanks
>Eric

That's one bad side. New data structures mean a new executable.
more cons:
* tables (and indexes) become corrupted, too, and more so than the dbc. With a tool like SDT, you can fix this, but the DBC has to be there.
* if users decide to get under the hood, they can try to use a table. They'll see the message that it can't find the database the table is linked to, with the option to remove the link. If they choose to delete the link, say hello to a nice piece of repair work, especially if you have long field names.