Problem Importing To A Clone

[kgasman]

I have a database I created for my wife's therapy practice. From time to time I make changes to scripts and database structure. In the past I have made a clone of the updated database and then manually imported the data from my wife's file into the updated clone. I thought I could create a script using the "import records" script step to automate this but one table will not import. Let me explain

The database consistes of five tables

Clients...this table contains the demographics of the client. "clientID" is the related record to

Billing...this table contains records of each billing and payments for the client ("clientID" is the related record)

notes...this table contains records of each of the therapy sessions for the client ("clientID" is the related record)

preferences... this table has one record with all the preference settings for the file

values... this table has multiple records for use in value lists during data entry.

I can manually import the data into each of these tables. the problem is when I automate it by

go to layout preferences

import records

go to layout values

import records

go to layout billings

import records

go to layout notes

import records

go to layout clients

import records

all the tables import except billings, it is always grayed out in the import dialog box

any ideas?

thank you

[bcooney]

It is import when you do this that you navigate to a layout that is based on the destination table. I cannot tell if the "Billings" layout is truly based on the Billings table.

I usually devote a "dev" layout to each table. This is the layout that I use for any import routines.

Also, remember to set your next serial number counters!

See this demo of an upgrade routine.

Upgrade Demo

[kgasman]

It is import when you do this that you navigate to a layout that is based on the destination table. I cannot tell if the "Billings" layout is truly based on the Billings table.

I usually devote a "dev" layout to each table. This is the layout that I use for any import routines.

Also, remember to set your next serial number counters!

See this demo of an upgrade routine.

Upgrade Demo

Yes Billings is based on Billings table.

I downloaded the demo. I will play with it to see how it works. thank you!!!

Is there a particular order I should import the tables. Since the "Clients" table is related to many billings in the "Billings" table and the "Clients" table is related to many notes in the "Notes" table, I thought I would have to import the "Billings" table then the "Notes" table then the "Clients" table. Then I would reset the "clientID" field serial number. It didn't seem important when I import the "Preferences" table or "Values" table as these are for lookup purposes only.

thanks for any help in advance

[kgasman]

It is import when you do this that you navigate to a layout that is based on the destination table. I cannot tell if the "Billings" layout is truly based on the Billings table.

I usually devote a "dev" layout to each table. This is the layout that I use for any import routines.

Also, remember to set your next serial number counters!

See this demo of an upgrade routine.

Upgrade Demo

Here is a problem with upgrade routine.

I have five tables to import. Using the import records script; the script step does not select the correct table to import to the current layout (table).

any thoughts

Kevin

[bcooney]

When I build the script, I add the source file manually so that I can set the field import mapping. After I test the script, I delete the "hard-coded" path to the source. You cannot specify field mapping just using a variable as the source path.

[kgasman]

When I build the script, I add the source file manually so that I can set the field import mapping. After I test the script, I delete the "hard-coded" path to the source. You cannot specify field mapping just using a variable as the source path.

thanks I will try that.

So I understand....

When I change the import script step from the "hard-coded" path to the reference; the field mapping will be maintained?

[bcooney]

Yes. In fact, you could leave the second path in the specify source dialog if you want.

[kgasman]

Yes. In fact, you could leave the second path in the specify source dialog if you want.

I will not do that since when I give the solution to my wife she will install it on her computer. I will not know the path in her computer. I guess that is why the reference path is so useful.

thanks for all the help