Heads up on "reindex"....

[Brian K. White]

----- Original Message ----- 
From: "GCC Consulting" <gccconsulting at comcast.net>
To: "'Bruce Easton'" <bruce at stn.com>; <filepro-list at lists.celestial.com>
Sent: Thursday, May 10, 2007 12:46 PM
Subject: RE: Heads up on "reindex"....


>
>
>> -----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 Bruce Easton
>> Sent: Thursday, May 10, 2007 12:08 PM
>> To: filepro-list at lists.celestial.com
>> Subject: RE: Heads up on "reindex"....
>>
>> Bruce wrote:
>>
>> > Jay Ashworth wrote Thursday, May 10, 2007 10:22 AM:
>> >
>> > [..]
>> >> While filePro makes it easy for end-users to *add* indexes
>> to files
>> >> to make it easier for them to search for things 'their
>> way'... it's
>> >> always annoyed me (WISHLIST) that there is no way for application
>> >> writers to
>> >> *lock* indexes so that the end user cannot touch them -- 
>> since as we
>> >> all know, extending an index *one character* can cause an entire
>> >> application to blow sky high.
>> >>
>> >[..]
>> >
>> > Now that you mention it, Jay, it does seem a bit strange that as
>> > over-zealous as the creation password implementation has
>> become with
>> > wildcarded filenames (causing enforcement to bleed over
>> into runtime
>> > programs) that it does not also encompass index maintenance.
>> >
>> > Perhaps filepro needs a new separate standard index-maint.
>> interface
>> > that could be used by clients that would only rebuild indexes.
>>
>> call it rxmaint  :)
>>
>> > Then
>> > the current dxmaint interface could be modified to employ, as you
>> > said, some sort of locking mechanism or password control (for the
>> > adding/modification side of things).  Of course, since I feel the
>> > creation password implementation has gone astray, if passwording is
>> > considered, I would not suggest using it.
>>
>> Bruce
>>
>> Bruce Easton
>> STN, Inc.
>
> With a little bit of programming one could write this interface using the
> tools within filepro.
>
> Use opendir to read in all of the available files to an array;  Then use a
> list box to display the file names.  Allow for selection of a file, then
> read in the available indexes, again display using a listbox.
>
> Next build the command line for the selected index and system out to run 
> it.
>
> Rebuild without the ability to change or add an index.
>
> Or simpler, at least for auto indexes dxmaint !! -ra -e from a user menu 
> and
> allow them to select the file to rebuild all of the auto indexes.  Or one
> could add an option to the above programming to the same, Have the last
> option "Rebuild All".
>
> So one could say you have the available tools for rindex now, as this can 
> be
> run from a library file, rather then waiting for fptech to implement this.
>
> Richard Kreiss
> GCC Consulting

Similarly a simple util to delete menus and output formats and other things 
which can be created at will but not deleted through the normal interfaces.

Brian K. White    brian at aljex.com    http://www.myspace.com/KEYofR
+++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++.
filePro  BBx    Linux  SCO  FreeBSD    #callahans  Satriani  Filk!