Announcement

Collapse

The Alpha Software Forum Participation Guidelines

The Alpha Software Forum is a free forum created for Alpha Software Developer Community to ask for help, exchange ideas, and share solutions. Alpha Software strives to create an environment where all members of the community can feel safe to participate. In order to ensure the Alpha Software Forum is a place where all feel welcome, forum participants are expected to behave as follows:
  • Be professional in your conduct
  • Be kind to others
  • Be constructive when giving feedback
  • Be open to new ideas and suggestions
  • Stay on topic


Be sure all comments and threads you post are respectful. Posts that contain any of the following content will be considered a violation of your agreement as a member of the Alpha Software Forum Community and will be moderated:
  • Spam.
  • Vulgar language.
  • Quotes from private conversations without permission, including pricing and other sales related discussions.
  • Personal attacks, insults, or subtle put-downs.
  • Harassment, bullying, threatening, mocking, shaming, or deriding anyone.
  • Sexist, racist, homophobic, transphobic, ableist, or otherwise discriminatory jokes and language.
  • Sexually explicit or violent material, links, or language.
  • Pirated, hacked, or copyright-infringing material.
  • Encouraging of others to engage in the above behaviors.


If a thread or post is found to contain any of the content outlined above, a moderator may choose to take one of the following actions:
  • Remove the Post or Thread - the content is removed from the forum.
  • Place the User in Moderation - all posts and new threads must be approved by a moderator before they are posted.
  • Temporarily Ban the User - user is banned from forum for a period of time.
  • Permanently Ban the User - user is permanently banned from the forum.


Moderators may also rename posts and threads if they are too generic or do not property reflect the content.

Moderators may move threads if they have been posted in the incorrect forum.

Threads/Posts questioning specific moderator decisions or actions (such as "why was a user banned?") are not allowed and will be removed.

The owners of Alpha Software Corporation (Forum Owner) reserve the right to remove, edit, move, or close any thread for any reason; or ban any forum member without notice, reason, or explanation.

Community members are encouraged to click the "Report Post" icon in the lower left of a given post if they feel the post is in violation of the rules. This will alert the Moderators to take a look.

Alpha Software Corporation may amend the guidelines from time to time and may also vary the procedures it sets out where appropriate in a particular case. Your agreement to comply with the guidelines will be deemed agreement to any changes to it.



Bonus TIPS for Successful Posting

Try a Search First
It is highly recommended that a Search be done on your topic before posting, as many questions have been answered in prior posts. As with any search engine, the shorter the search term, the more "hits" will be returned, but the more specific the search term is, the greater the relevance of those "hits". Searching for "table" might well return every message on the board while "tablesum" would greatly restrict the number of messages returned.

When you do post
First, make sure you are posting your question in the correct forum. For example, if you post an issue regarding Desktop applications on the Mobile & Browser Applications board , not only will your question not be seen by the appropriate audience, it may also be removed or relocated.

The more detail you provide about your problem or question, the more likely someone is to understand your request and be able to help. A sample database with a minimum of records (and its support files, zipped together) will make it much easier to diagnose issues with your application. Screen shots of error messages are especially helpful.

When explaining how to reproduce your problem, please be as detailed as possible. Describe every step, click-by-click and keypress-by-keypress. Otherwise when others try to duplicate your problem, they may do something slightly different and end up with different results.

A note about attachments
You may only attach one file to each message. Attachment file size is limited to 2MB. If you need to include several files, you may do so by zipping them into a single archive.

If you forgot to attach your files to your post, please do NOT create a new thread. Instead, reply to your original message and attach the file there.

When attaching screen shots, it is best to attach an image file (.BMP, .JPG, .GIF, .PNG, etc.) or a zip file of several images, as opposed to a Word document containing the screen shots. Because Word documents are prone to viruses, many message board users will not open your Word file, therefore limiting their ability to help you.

Similarly, if you are uploading a zipped archive, you should simply create a .ZIP file and not a self-extracting .EXE as many users will not run your EXE file.
See more
See less

for each...next loops

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • for each...next loops

    This is a bit of a general question, but I'm using in my web app, so...

    Is there any functional limit I'm not aware of regarding for each..next loops? Is there any problem nesting them? I don't see why either should be problematic, but I can't figure it out.

    I'm only cycling through about 57 records, so it should be able to handle it. Hopefully someone will see something I'm missing.

    PHP Code:
    dim spend_table as p
    dim bank_table 
    as p
    dim CompDiscInfo 
    as c
    dim EmployeeIDList 
    as c
    dim EmployeeCompDisc 
    as c
    dim hours_remaining 
    as n
    dim hours_to_post 
    as n
    dim hours_available 
    as n
    dim hour_check 
    as n
    DIM bank_list 
    AS C
    DIM find_result 
    AS N
    DIM indx 
    AS P
    DIM result 
    AS N

    spend_table 
    table.open("[PathAlias.ADB_Path]\compspent")
    bank_table table.open("[PathAlias.ADB_Path]\compbank")

    EmployeeIDList word_unique(table.external_record_content_get("[PathAlias.ADB_Path]\workhours","emp_id","emp_id","work_type='Comp Disc'.and.work_date>{3/11/2008}"),crlf())
    CompDiscInfo table.external_record_content_get("[PathAlias.ADB_Path]\workhours","work_id+'|'+work_date+'|'+work_hrs+'|'+emp_id","emp_id+work_date","work_type='Comp Disc'.and.work_date>{3/11/2008}")

    for 
    each EmployeeID in EmployeeIDList
        EmployeeCompDisc 
    filter_string(CompDiscInfo,EmployeeID)
        for 
    each Discharge in EmployeeCompDisc
            hour_check 
    tablesum("[PathAlias.ADB_Path]\compbank""hrs_earned>hrs_spent.and.between(comp_date, (addmonths({" word(Discharge,2,"|") + "},-3)+1), {" word(Discharge,2,"|") + "}-1).and.emp_id='" EmployeeID "'.and..not.is_del""hrs_earned")
            
    hours_remaining val(word(Discharge,3,"|"))
            if 
    hours_remaining <= hour_check then
                bank_list 
    table.external_record_content_get("[PathAlias.ADB_Path]\compbank","comp_id+'|'+comp_date+'|'+hrs_earned+'|'+hrs_spent","comp_date","hrs_earned>hrs_spent.and.between(comp_date, (addmonths({" word(Discharge,2,"|") + "},-3)+1), {" word(Discharge,2,"|") + "}-1).and.emp_id='" EmployeeID "'.and..not.is_del")
                for 
    each entry in bank_list
                    hours_available 
    val(word(entry,3,"|")) - val(word(entry,4,"|"))
                    if 
    hours_remaining <= hours_available then
                        hours_to_post 
    hours_remaining
                        hours_remaining 
    0
                    
    else
                        
    hours_to_post hours_available
                        hours_remaining 
    hours_remaining hours_available
                    end 
    if
                    
    spend_table.enter_begin()
                        
    spend_table.Comp_id alltrim(word(entry,1,"|"))
                        
    spend_table.Work_id alltrim(word(Discharge,1,"|"))
                        
    spend_table.Emp_id alltrim(EmployeeID)
                        
    spend_table.Spent_date ctod(alltrim(word(Discharge,2,"|")))
                        
    spend_table.Hrs_spent hours_to_post
                        spend_table
    .Is_chg = .t.
                        
    spend_table.Chg_by_id currentReviewer
                        spend_table
    .Chg_date date()
                        
    spend_table.Doc now()
                    
    spend_table.enter_end()

                    
    bank_table.index_primary_put("comp_id")
                    
    find_result bank_table.fetch_find(word(entry,1,"|"))
                    if 
    find_result 0 then
                        bank_table
    .change_begin()
                            
    bank_table.Is_chg = .t.
                            
    bank_table.Chg_by_id currentRviewer
                            bank_table
    .Chg_date date()
                            
    bank_table.Hrs_spent bank_table.Hrs_spent hours_to_post
                        bank_table
    .change_end()
                    else
                        
    result ui_msg_box("ERROR""Error posting to COMPBANK (" ut(str(find_result)) + ")",UI_OK_CANCEL)
                        if 
    result UI_CANCEL_SELECTED then
                            end
                        end 
    if
                    
    end if
                    if 
    hours_remaining 0 then
                        
    exit for
                    
    end if
                    
    statusbar.Set_Text(EmployeeID "|" Discharge "|" entry)
                
    next entry
            
    else
                
    result ui_msg_box("Lack of hours","There are not enough hours to use.\n\nMissing " ut(str(hours_remaining hour_check)) + "hours.",UI_OK_CANCEL)
                if 
    result UI_CANCEL_SELECTED then
                    end
                
    else
                    continue
                
    end if
            
    end if
        
    next Discharge
    next EmployeeID

    spend_table
    .close()
    bank_table.close()

    statusbar.clear()
    ui_msg_box("Complete","The compAction routine has completed."
    Stephen Pilon
    Associate Librarian
    Christendom College

  • #2
    Re: for each...next loops

    I like it when I can answer my own question. As I suspected, I was not seeing where I was getting trapped. All fixed for now, thanks.
    Stephen Pilon
    Associate Librarian
    Christendom College

    Comment

    Working...
    X