FW: changing key size

[Dave Andersen]

> You could add a field denoting the origin of the data.

 

We considered this, but we think the application will break when it finds two records corresponding to 10000, because it doesn’t know about the origin field.  We want to avoid changing processing instructions during this phase.

 

Can you give any advice on how to write a script that adds a value to a certain field in each row of a table?

 

-----Original Message-----
From: Transpower at aol.com [mailto:Transpower at aol.com] 
Sent: Monday, August 30, 2004 4:11 PM
To: Dave Andersen
Subject: Re: changing key size

 

In a message dated 8/30/2004 6:36:33 PM Eastern Daylight Time, dave at PRIMUS.NET writes:



Hi, I’m new to filePro.  We have a customer who wants to merge 4 filePro databases together (identical schemas).  There is a problem with the key fields though, because each database started at 1.  So we want to prepend a value to the keys in each table to make them unique.  So record 10000 would become 110000 at location 1, and at location 2 10000 would become 210000.

  

It looks like the first task is to change the schema for each table and change “5 *” to “7 *” (widen the field).

  

At first our customer asked us to write a script to edit the table/Key file directly.  This seems like a bad idea because the file is not plain text and I’m pretty sure we would corrupt it.

  

So I guess we have two options: 1) figure out filePro processing or 2) export to csv, process the table with a script, re-import.

  

Can you give me some ideas where to start?  I’m confused on how to make a filePro script that would cycle through all the records.

  

Is the $190 filePro book worth it?



With identical schemas, you can pick one database file and have the other three post all their records to it (lookup file free, copy file).  You could add a field denoting the origin of the data.

Regards,
RWS
transpower at aol.com
www.transpowercorp.com
Commercial and custom software manufactuing for engineering and management since 1976; SCO Authorized and Microsoft Certified Systems Engineering

 

---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.737 / Virus Database: 491 - Release Date: 8/11/2004


---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.737 / Virus Database: 491 - Release Date: 8/11/2004



---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.737 / Virus Database: 491 - Release Date: 8/11/2004
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.celestial.com/pipermail/filepro-list/attachments/20040830/44e1ce6c/attachment-0001.html