Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!
  • Students Click Here

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here


Progress bar with DBFCDX indexes

Progress bar with DBFCDX indexes

Progress bar with DBFCDX indexes

I have a utility which reindexes a whole bunch of tables.  When I used DBFNTX I used to display a progress bar

INDEX ON Accno+DTOS(DATE)+MyRef TO MyFile1.NTX EVAL ShowProg("MyFile") EVERY 20

ShowProg() would then do some sums and display a progress bar.

Now that I am using DBFCDX, I say :

INDEX ON Accno+DTOS(DATE)+MyRef TAG MyIdx1 TO MyFile EVAL ShowProg("MyFile") EVERY 20

This does not work, because I believe that the EVAL clause is not being executed.  Has anyone tried this, and is there a work-around?



RE: Progress bar with DBFCDX indexes

You didn't share the code for ShowProg(), could this be the cause?


4.5  DBFCDX Driver note
   EVAL and EVERY clauses of the INDEX ON command
   The EVAL clause functions differently in the DBFCDX driver than it
   does in other RDDs.  The EVAL block is evaluated at the beginning
   and at the end of each indexing process as well as at each record
   as in other RDDs.  At the beginning of the index process both
   BOF() and EOF() are true (.T.).  At the end of the indexing
   process only EOF() is true (.T.).
Ref: http://www.sigaconsult.com.br/manuais/files/cdutil/clipper/DISK1/README


---People Remember about 10% of what you say ---They never forget how you made them feel.  Covey

RE: Progress bar with DBFCDX indexes

......EVERY LASTREC()/20



RE: Progress bar with DBFCDX indexes

Thank you both for your suggestions

In fact the fault was mine.  The EVAL function was being called.  It was just that the time spent opening and closing the indexes was large compared to the time processing the records (these were fairly small tables), so the progress bar always seemed to be at 0% or 100%.

Sorry for the false alarm.  Andrew

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members!

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close