changing key size

[GCC Consulting]

  _____  

From: filepro-list-bounces at lists.celestial.com
[mailto:filepro-list-bounces at lists.celestial.com] On Behalf Of Dave Andersen
Sent: Monday, August 30, 2004 6:35 PM
To: filepro-list at seaslug.org
Subject: changing key size



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?

 

 

First, Yes the Developer's Reference is worth it.  However there are a number of
other sources for for filePro help.  You might look at Lara Brody's site
http://www.hvcomputer.com/  and you could check Nancy Palmquist's site
<http://www.vss3.com> http://www.vss3.com.  Both sites have valuable information
about filepro.

 

Another place for help is th filepro chatroom
http://www.talkingcommunities.com/ivocalize.pl?server=1001
<http://www.talkingcommunities.com/ivocalize.pl?server=1001&secure=John&room=The
_FP_Room&pass=&/> &secure=John&room=The_FP_Room&pass=&/

 

This is a live place to talk with other filepro programmers.  All you need are
speakers & a mike.  

 

What version of fp are they running.

 

As for your problem, I would suggest that you:

    1. Uualify on of the files, assuming that the file is not already qualified.

    2.  Add the the necessary field to all of the databases

    3. Expand the new qualified file to a value somewhat greater then the total
records for the databases.

    4. Create a process that posts each record according to which record # you
want.

 

Now, before you do this, are you using the record #'s as a lookup value?  If so,
why.

 

A suggestion, since many of the developers in the "list" are using *nix, in the
future, sent you e-mails in plain text.  Their e-mail clients many time does not
display this format properly and they will ignore the posting.

 

I'm one of those who does use Outlook and can easily read this posting.

 

Richard Kreiss
GCC Consulting 

 

 

 

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.celestial.com/pipermail/filepro-list/attachments/20040830/00d4683d/attachment-0001.html