>hi
>thank you for your info. Do you think it will make the application not flexible and diff to be extend?

Well, one reason I prefer to integrate is because some tables might be shared, and some forms might be used in more than one module. For instance, this might be the case with a table and form for manipulating clients.

Of course, an integrated system might require updates from one table to another one, for instance. But you might need to do this sort of integration anyway, if you want to offer several modules to a single client.

Perhaps storing certain information in tables might help to resolve some of your issues. For instance, for most forms, I don't put a command to open it in the menu. Instead, I have a single form, that is opened with "File | Open", that lists the available forms. The list of available forms is dependent on the user-level, and on the department or workgroup (Accounting, Sales, etc.). A "forms" table stores information on each form: what is the minimum user-level required to open it, and for what departments the form is relevant.

You could adapt this, to store information about each form: "This form is required for modules X, Y, and Z".

In summary, no, I don't think it should be too difficult to extend, but some careful planning will be helpful.

HTH, Hilmar.