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

Pointer Variables

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

    Pointer Variables

    I would like to use a variable to load the name of a field in a record that I would like to update. But I'm thinking I may need to use the Pointer variable type and I don't understand the documentation in the book.

    Here is the plain english code that I would like to use:

    tbl.open table
    find record to update
    based on the values of the record (a series of in and out time clock punches) load a variable called "punch" with the name of the field that is to hold the next "punch"
    tbl.change begin
    tbl.punch=time()
    change end
    tbl.close

    Can I load my field name into the variable call punch? and if so do I need to declare the variable in a special way? and once doing this what does the assignment statement look like?

    Thanks for the help!!!

    #2
    RE: Pointer Variables

    Rhett,

    I'll give this some thought.

    In the meantime, I'm curious about something. why not put the in and out times in a linked one to many child table, instead of having multiple instances in each record? Unless I miss my guess your design is better suited for a spreadsheet than a relational dbf.

    Code:
    employee
      ||
       ==>TimeRecords

    Where employee table contains one unique record per employee, and includes an idnumber of some sort, and
    TimeRecords includes lots and lots of records, each of which includes an idnumber linking the current record back to the Employee table.

    TimeRecords table could have this kind of structure:
    Code:
    idnum,   c,   5
    dateworked,    d,    8
    clockin,   c,   6
    clockout,   c,   6
    and so on.

    More later,

    -- tom

    Comment


      #3
      RE: Pointer Variables

      Rhett,

      here's an example to play with that might help.

      Unzip to a separate folder. Do not mix with your development work.

      -- tom

      Comment


        #4
        RE: Pointer Variables

        Rhett,

        the example in the previous post illustrates how to change the value stored in a field in a table, when the user specifies the name of the field, and supplies the new value.

        It does this in Xbasic by getting a pointer to the desired field, and then using the fld.value_put() method. Something similar could be easily adapted for your case I believe.

        -- tom

        Comment


          #5
          RE: Pointer Variables

          Here's how I did a time clock app. This is only part of it and it's not done. The part that they punch in on is in one database and the reports etc are in a different database for security reasons. Unzip this to a new directory. This should work but I did a backup and didn't test the backup. The approach here is pretty much what Tom is talking about. (And I'm sure he could do it better)

          Russ

          Comment

          Working...
          X