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

field update

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

  • field update

    Hi Phorum,

    I have created an operation/update to update a field (c:\dos_zip\dues.dbf (char,11)from c:\program files\a5v4\union\dues.dbf. I am using the following expression;

    STRTRAN(SOC_SEC,"soc_sec=""","@c:\program files\union\members-"soc_sec")

    When I run the operation it states that 31,740 records had been updated.

    If I run it again it states the same thing when I expect it to say 0 records were updated. If I open the table I see that soc_sec is blank in all records.

    All suggestions will be gratefully accepted,
    efs

  • #2
    RE: field update

    Ed, I'm assuming you've given us the expression you're using to update the Soc_Sec field in the dos_zip\dues table. If so, it's time to hit the books. Check the docs on the STRTRAN() function.

    A rough translation of your expression is this:

    1) for each record in the dues table
    2) examine the Soc_Sec

    Comment


    • #3
      RE: field update

      Ed, I'm assuming you've given us the expression you're using to update the Soc_Sec field in the dos_zip\dues table. If so, it's time to hit the books. Check the docs on the STRTRAN() function.

      A rough translation of your expression is this:

      1) for each record in the dues table
      2) examine the Soc_Sec field to see if the string "soc_sec= """ is present
      3) if so, replace the Soc_Field value with "@c:\program files\union\members-"soc_sec"
      4) otherwise do nothing.

      So, all the records are checked and nothing is done. Over and over.

      Tell us what it is you really want to do.

      -- tom

      Comment


      • #4
        RE: field update

        Hi Tom,

        First off .... thank you for responding. I think you got the answer to what I want by reading your first reply.

        I want to fill in a blank soc_sec field in the C:\dos_zip\ dues.dbf with data from (soc_sec)c:\program files\a5v4\union\dues.dbf.

        Thanks again for your time,
        Ed

        Comment


        • #5
          RE: field update

          Ed,

          I'd begin by thinking of how I'd do this one at a time. First thought here is that I'd use the lookup() function to retrieve the correct SSAN from the source table, and then write it to the target table in the correct record. I believe the lookup() funciton is what you could use to do this across the entire table, using an Update operation defined for the target table.

          What prompted you to try STRITRAN() ?

          -- tom

          Comment


          • #6
            RE: field update

            Hi Tom,

            Thank you again for replying. A couple of years ago I used the same expression in an update and it worked very well in this same application. Now about 2 or more years later the union was forced to dig up some very old data from the archives that had not had a soc_sec field in it at the time since data at that time was not needed for data that old. But when the union was suddenly required to save their data differently it became necessary to use a set and at that time someone in the forum suggested I use the strtran to update the dues table in order to provide a good linking field between the members table and the dues table, as I had said earlier it did the job very well. Why it worked then but not now is beyond me.

            I also found an append in an old version that for unknown reasons also that works very well on about 75% of the records. it seems to me that I probaly used the append at that time. Curiously, I ran the update after he append and it deleted soc_sec in all of the dues table records.

            Thanks again,
            Ed

            Comment


            • #7
              RE: field update

              Hi Tom,

              I don't know why I did not use the lookup in the first place (it seems to be the easiest way). However I just put it in the soc_sec field rules of the target table and it did the same thing as the append operation, meaning that it covered about 75% of the records. Why it doesn't work on all of them is for agent 007 to solve.

              Agent 001 (Ed)

              Comment


              • #8
                RE: field update

                Maybe some folks have joined up for whom you never collected SSAN information????

                -- tom

                Comment


                • #9
                  RE: field update

                  Maybe some of the members' names are spelled differently in the two tables????

                  -- tom

                  Comment


                  • #10
                    RE: field update

                    Hi Tom,

                    I just noticed that the ones that did not get get updated are duplicates. I will now delete the dupes.
                    Thanks again,
                    Ed

                    Comment

                    Working...
                    X