>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
There is also one solution which helps to minimize DBC corruption problems. You may have the DBC locally for every client. Say, you have a local EXE which on application startup copies the good known and recent copy of the DBC from some network share to the local drive. Optionally the Launcher.exe may do the checking and updates for both app EXE, DBC and any other related files.
Nick Neklioudov
Universal Thread Consultant
3 times Microsoft MVP - Visual FoxPro
"I have not failed. I've just found 10,000 ways that don't work." - Thomas Edison