Hello,
Instead of using an access/sql database for each language, can't that be 1 for all? Let's have 1 database that have all of the material selected and when a language pack is install, let it do a commit on the master database instead, updating it with a new table for the new language. Thus, you would have a database of all the pieces selected for install then a table for the matching language. When a new language is added, simply add the new table. So when browsing through the catalog, everything will be reference by an ID of a piece. Only two table will be loaded at a time, current language and parts. If a language table is not found, revert to installation default.
Thank you
