Alpha Software Mobile Development Tools:   Alpha Anywhere    |   Alpha TransForm subscribe to our YouTube Channel  Follow Us on LinkedIn  Follow Us on Twitter  Follow Us on Facebook

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

Time Clock-Code help

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

    Time Clock-Code help

    Hi everyone,

    I have the following code on a button "Punch In" on a form for a time clock app- this is in A5v5 b1050 but the problem is not alpha it's me I'm sure.
    The e.punch_status.value="I" doesn't work.It generates an error that the field is locked because it is in use by another process and nothing is put in the field. The field Punch_status is on the form and shows in the object explorer.
    I can post the form if necessary. I'm stumped (doesn't take much to stump me!)
    Thanks in advance for your help.

    'Employee enters employee number, if valid can press punch in or punch out
    'of not valid empno pops up filtered lookup on employee where current(.t.) and hourly(.t.)
    'can double click on name in lookup to enter empno in field.
    'Clicking on punch in or punch out is now allowed.
    'When click on Punch In:
    'Save record in current form.
    topparent.commit()

    'put value in field DUMHOUR->EMPNO into variable VEMPNO
    t=table.open("dumhour")
    dim global vempno as c
    vempno=t.EMPNO
    t.close()

    'Find out if employee "vempno" is punched in (employee->punch_status="I")
    if Punch_status.value="I" then
    ui_msg_box("Punch In?","Your Are Already Punched In!",UI_ATTENTION_SYMBOL)
    end
    end if

    'do nothing if the empno field is blank
    if empno0.value="" then
    ui_msg_box("Employee Number","You must enter your employee number!",UI_STOP_SYMBOL)
    end
    end if

    'Make an entry in the HOURSPR table
    dim tbl as p
    tbl = table.open("hourspr",FILE_RW_EXCLUSIVE)
    tbl.enter_begin()
    tbl.EMPNO = vempno
    tbl.DATE_IN = Date()
    tbl.TIME_IN = Time()
    tbl.enter_end(.t.)
    tbl.close()

    e = table.open("employee")
    e.change_begin()
    e.Punch_status.value = "I" 'this doesn't put value in
    e.change_end()
    e.close()


    'clean out dumhour
    t=table.open("dumhour")
    t.zap(.t.)
    t.close()

    parentform.Resynch()

    #2
    RE: Time Clock-Code help

    e.Punch_status.value = "I" 'this doesn't put value in
    ------------------------------
    You're using a form method here instead of a table method.

    Should be"
    e.punch_status = "I"

    Comment


      #3
      RE: Time Clock-Code help

      steve is right, but even if you make his change, the code

      e = table.open("employee")
      e.change_begin()
      e.Punch_status = "I"
      e.change_end()
      e.close()
      will always change the first record in the
      employee table. Is that what you want? isn't there more
      than one record in the table?

      Comment


        #4
        RE: Time Clock-Code help

        Thanks,
        Yes, there are more records in the employee table, I only want to change the current one -which is the one that is displayed on the form. The set is:
        Dumhour
        |--->Employee

        The employee represented by the value un the empno field on Dumhour is the employee that is displayed on the form. I am using a dummy table for the parent so I can zap it after each punch so the next employee is presented a blank field in which to put his employee code. The link is on empno. This is my first try at something more complex than changing forms and setting indexes so I appreciate the help.

        I can post the sets tonite if it would help to see them.

        Russ

        Comment


          #5
          RE: Time Clock-Code help

          I, too, agree with Dr. Wayne. I have no clue why this code works. Your opening a new instance of the table with the table.open command; therefore, the records are no longer synched--you're simply writing and reading from the first record. Unable to fathom your code, I simply indicated why your table write failed. I think you should review this entire procedure to see if it is doing what you really want it do.

          Comment


            #6
            RE: Time Clock-Code help

            I'll post the form as soon as I get a chance. I see why this wouldn't work as written so I'll try another method before posting it. I can see it'll take a while to get the hang of this.

            Russ

            Comment


              #7
              RE: Time Clock-Code help

              you can just make it

              Punch_status.value = "I"

              assuming that punch_status is the name of the field
              on the form. you will then be changing the value
              of the field on the form, directly.
              if the employee table is displayed as a browse and
              not as fields on a form, you can write

              e = table.get("employee")
              e.change_begin()
              e.Punch_status = "I"
              e.change_end()

              in the second instance "e" becomes attached to the
              form's own pointer to the employee table, and is therefore
              automatically on the right record. notice when you use
              table.get() you do not close the pointer afterwards.

              - peter

              Comment


                #8
                RE: Time Clock-Code help

                Thank you Peter
                It now seems so logical! I'll do that. One thing though should I remove the parentform.commit or will it change the field regardless? I guess I shouldn't ask that question since I can try it to find out.

                Thanks again
                Russ

                Comment

                Working...
                X