John,

Thanks for your reply. When I first developed this system I actually started to do this but never fully implemented the code because I thought it was too complicated. Now, that I have to I guess I will just complete the job. Being only a part time programmer, I just wanted the simplest and quickest solution, and it sounds like this is it. Thanks again.

Peter

>Hi Peter ---

>I don't want to sound cryptic, but the *best* way to do this should be dictated by business needs and process.
>
>That being said, try this: Keep your existing file structure as is, with the exception that you add a country code column to customer and receivables. Create new child tables for those two tables that link to the primary key of the parents to track information applicable to Canada. Where access to those tables requires a delineation of countries, use paramterized views.
>
>You really want to avoid having two tables with the same name and/or purpose when a simple "type" code solves the problem.


>>I have developed a system we use internally for keeping track of customer sales info, inventory and receivables. We have now just begun adding a new country, ie Canada, and I need to create new files of customer and receivables information (there will be new fields added), but use existing inventory files.
>>
>>I have all files currently in a database. Any suggestions on what is the easiest and simplest way to do this? Back in the old Clipper DOS days I used to just create the new files in a new directory and set the path to this directory first, then the existing directory. But the files now are all in a database.
>>