Merge Data/Key Files
GCC Consulting
gccconsulting at comcast.net
Fri Jul 6 09:27:51 PDT 2007
> -----Original Message-----
> From:
> filepro-list-bounces+gccconsulting=comcast.net at lists.celestial
> .com
> [mailto:filepro-list-bounces+gccconsulting=comcast.net at lists.c
> elestial.com] On Behalf Of Clay Brown
> Sent: Wednesday, July 04, 2007 1:36 PM
> To: Pete Murray; filepro-list at lists.celestial.com
> Subject: Re: Merge Data/Key Files
>
> Everyone knows about the problem. I Believe that every menu
> is a separate entity. I was thinking after they closed
> yesterday that if the only one to make changes to the file
> was the local copy i could just replace the entire
> f:\filepro\dajuror directory. I of course will make a backup
> of it first. Or even if only small changes were made by
> others the local copy I know made major and most of the
> changes. the Good news is these records are only edited and
> added to once a month and not daily so there was not as many
> changes as say the Worthless Check Div where there is 1-2
> users adding and appending records every day all day. I'll
> let you guys know something tomorrow morning. The Goverment
> offices are of course closed today so I cant make a trip
> there. Just came into the office to work on a repeater and
> check the email
>
>
> Thanks for all the Insight.
>
> Clay
>
>
> ----- Original Message -----
> From: Pete Murray
> To: filepro-list at lists.celestial.com
> Sent: Tuesday, July 03, 2007 9:15 PM
> Subject: Re: Merge Data/Key Files
>
>
> Did anybody else edit the juror file during that time?
> Do you know or think that, while the person was editing the
> juror file on
> the local machine, they might have caused
> changes in other files?
> Has or will the current problem effected the actual court sytem?
> I've found that in situations like this that could have
> serious effects, it
> has been best to get the situation in the open before rather
> than after.
>
>
A little late to this thread but the simplest way would, if possible,
qualify your network files. Copy the data form the local drive to
filename\key.qual and then write a posting program which checks the last
updates date and compare the fields. Post those that changed and create new
records for those that don't exist.
The harder problem is the first one, posting changed data. After the
update, delete the qualified key and indexes.
Richard Kreiss
GCC Consulting
More information about the Filepro-list
mailing list