>Josh,
>
>Thank you for your suggestion :-)
>
>You're right, it is fully documented.
>
>The main database already contains about 65 tables and about 170 local views !
>We have to import another database with about 50 tables and about 50 views !
>
>I'm not sure we have time enough to program a tool in order to do that merge operation but we will try if we don't find any other "faster" solution.
>
>Regards,
>Jean-Pol.

Jean-Pol,

First of all, I'd carefully check the docs about the features xCase has to offer, but I am not too sure it should be doable, because it plays with a model at a time. As far as I know you cannot build a view based on a table in another DBC.

What you could do, however, is generate your B.DBC code with the help of GENDBCx and apply this code to you A.DBC.

By doing so you'll be able to get everything from B into A. That done, from VFP you could update the xCase model from the DBC. And all would be done. Well, not exactly. Since the views will not be migrated into xCase.

Another point, I see you are still with xCase 2.5. xCase 4 has improvements that make the upgrade quite valuable. My favourite are views of views (really easy) and an improved interface (the links are easier to move and will stay where you want them to stay...)

José