Talking databases

[Nathan Lehman]

  Thanks Nancy.  That is a pretty cool trick.  However, I don't want the
two databases to share all of the data in that table.  I just need to be
able to share a couple of fields in "like" records.  So far the easiest
way I can see how to do this is to take Richard's suggestion and set up
a scheduled export and import to run on both databases every so often.
It isn't pretty and it isn't real time, but it gets the job done.

> -----Original Message-----
> From: Nancy Palmquist [mailto:nlp at vss3.com]
> Sent: Tuesday, January 10, 2006 12:53 PM
> To: Nathan Lehman
> Cc: filepro-list at lists.celestial.com
> Subject: Re: Talking databases
> 
> Nathan,
> 
> The solution to this is much easier than I see postings from others.
> 
> FilePro will allow data to be stored on more than one drive.
> 
> For example:
> 
> F:\filepro\taxtable\key		My novell live system
> G:\filepro\taxtable\key		My test system.
> 
> Now you use these based on the PFDATA variable set PFDATA=F: for live
> and set PFDATA=G: for test.  You also set PFDSK=F for live and PFDSK=G
> for test to keep each only looking at the correct drive.
> 
> If you add a drive S: so you have:
> 
> S:\filepro\taxtable\key
> 
> Add S to the PFDSK for both sides.
> 
> Remove the key from f: and G: for the files in question. (RENAME THEM
> Until you are sure it works.)
> 
> You can also put the indexes on the S: and remove them from the F and
G
> drives.  All programming stays on the F and G drives as well as the
map.
> 
> It will share the data completely between the two systems with no
problem.
> 
> GOTCHA 1 - Be real careful about restructures - changing the file
> definition for any reason.  You might want to make the map read-only
as
> a reminder.  Allow restructure from only one place then copy the
changed
> map to the other side from windows.
> 
> GOTCHA 2- I haven't tried this lately, but in tests in the past, the
> indexes rebuilt on the first drive, instead of where they have been
> moved.  I think that is fixed, but have not tried it lately.
> 
> GOTCHA 3- Lockfile is always placed on the first drive, so even moving
> it to the second drive does no good about file locking.  RECORD
locking
> works just fine on a network computer.
> 
> Best success with code files that are not updated often, it is a great
> trick and can be used on many system types.
> 
> I even use it to share data between Linux and Windows systems.  It
works
> great for that also.
> 
> If filePro would allow the lockfile to be moved to any one of the
> mounted folders and the indexes stayed where you put them, it would be
> perfect.  (Without checking, I can't remember about the indexes they
may
> stick fine these days.)
> 
> This all works on a Linux/Unix system also, by using PFDSK=/var1:/var2
> to set the locations and under those folders the same folders must
exist
> (filepro/filename) or (appl/filepro/filename)
> 
> Just a suggestion.
> 
> Nancy
> 
> 
> 
> 
> --
> Nancy Palmquist 		MOS & filePro Training Available
> Virtual Software Systems	Web Based Training and Consulting
> PHONE: (412) 835-9417		   Web site:  http://www.vss3.com