Copy Table to Another DB (UnLinked)

[Sorrells]

I would like to copy about 6 tables in a Program_db with client data into new tables in a Data_db where the new table has the same name but with a Client_Prefix (eg sd_).

I ran across the CopyOject Action that performs the task with one exception, the copied table in the data_db is linked to the Program_db. In the help topics there is no mention that the tables are linked nor do I see a way to break the link so that the table is whole in the Data_db.

Obviously there are many ways around this but I surely would appreciate advice on the most efficient one. The following possibilities come to mind:

1) Add a field to each of the client sensitive tables to hold a 'Client Index Number' that can be related to the Client_Prefix [I like this but will have to perform some retrofitting]

2) Create the table structures from scratch in the Data_db then copy the data into them. [Assuming that I can create a table in an external DB, seems possible. Reluctant to code all the fields to be entered.]

3) Break the shackle links from the new tables in the external dB. [I bet this cannot be done]

4) Any others????

I'd appreciate any advice. If the above set is all there is, I'd go with number 1 if there were not any more input. So perhaps someone might save me from myself?!?

Regards, Sorrells

 

[doulostheou]

I don't think I understand your problem correctly. Why don't you just import the tables and rename them?

 

[Pat Hartman]

The TransferDatabase Method should allow you to create tables in another db.

However, I would NOT create separate tables for each client. You are making a maintenance nightmare by doing that. Go with option 1 and add a column to the table so you can use filters to control access to sensitive data.