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

Writing to a table ignoring field rules

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

    Writing to a table ignoring field rules

    I have the following code that writes a record to a table:

    Code:
    DIM doctbl as P
    doctbl = table.open("Faxes_Sent",FILE_RW_SHARED)
    doctbl.enter_begin()
    doctbl.tracking=alltrim(str(val(case->Case_Id)))
    doctbl.Fax_Num=substr(zip->fax_num,1,10)
    doctbl.date_sent=Date()
    doctbl.Time_Sent=time("0h:0m:0s")
    doctbl.Rejected=.f.
    doctbl.enter_end(.t.)
    doctbl.close()
    This works fine, except in the table "faxes_sent", the "fax_num" field has a field rule defined as "###-###-####".

    The above ignores the field rule and saves the field as ##########

    Is it possible to modify this so it honors the field rule settings?

    Thanks

    #2
    Might be easiest to format the fax# as nnn-nnn-nnnn before writing it.
    See our Hybrid Option here;
    https://hybridapps.example-software.com/


    Apologies to anyone I haven't managed to upset yet.
    You are held in a queue and I will get to you soon.

    Comment


      #3
      Originally posted by Ted Giles View Post
      Might be easiest to format the fax# as nnn-nnn-nnnn before writing it.
      Thanks, Ted...

      Thought that might be the case but I don't have any idea how to go about doing that.

      Thanks

      Comment


        #4
        See "Field Rules Honored During Xbasic Data Entry" from help.
        http://documentation.alphasoftware.c...ommitting%20It
        and there is some other function which Honored field rule other than "<tbl>.enter_begin()"

        Comment


          #5
          I believe you need to add the .t. argument in the enter_begin function so the enter will honor the field rules.

          doctbl.enter_begin(.t.)
          Alpha 5 Version 11
          AA Build 2999, Build 4269, Current Build
          DBF's and MySql
          Desktop, Web on the Desktop and WEB

          Ron Anusiewicz

          Comment


            #6
            I think adding the " .t. " parameter is worth a try. The helps indicate this enforces field rules if the code uses a pointer to a table that's supporting the current form. See: tbl.enter_begin Method

            The help system indicates this won't work when a new instance of the table is being opened by the code. But I think it's worth a try anyway.

            Comment


              #7
              Originally posted by Tom Cone Jr View Post
              I think adding the " .t. " parameter is worth a try. The helps indicate this enforces field rules if the code uses a pointer to a table that's supporting the current form. See: tbl.enter_begin Method

              The help system indicates this won't work when a new instance of the table is being opened by the code. But I think it's worth a try anyway.
              You're correct, Tom.

              Adding the .t. parameter did not work for the reason you stated.

              Is it possible to manipulate the data before writing it to the table?

              Thanks

              Comment


                #8
                You will need to research the way to split stuff up.
                Posting will honour field rules, and so does Append.
                See our Hybrid Option here;
                https://hybridapps.example-software.com/


                Apologies to anyone I haven't managed to upset yet.
                You are held in a queue and I will get to you soon.

                Comment


                  #9
                  Hi Mark,
                  I'm with Ted, format the value before/during writing to the tables. I frankly avoid field rules absolutely as much as possible and do the heavy lifting in the scripts. Avoids conflict like you are experiencing.
                  Mike W
                  __________________________
                  "I rebel in at least small things to express to the world that I have not completely surrendered"

                  Comment


                    #10
                    Mark, this is the logic for taking a Char field, chopping it up and reassembling it.
                    Taken from the Interactive Window. Copy the text into the I/w and try it out.

                    dim fax as c
                    fax = "1234567890" ' I am presuming that the fax# is stored as a character

                    ?fax
                    = "1234567890" 'to see if the value is populated

                    ? left(fax,3) ' left 3 values. Starts at place 1 and selects 3 characters
                    = "123"

                    ?mid(fax,4,3) ' mid values. Starts at place 4 for 3 characters
                    = "456"

                    ? right(fax,4) ' right values. Reads back 4 characters from the end
                    = "7890"

                    ? left(fax,3)+"-"+mid(fax,4,3)+"-"+right(fax,4) ' Assemble it and add the "-" as a separator. You only need this bit.
                    = "123-456-7890"


                    So in your script, the fax_num to be written might be

                    left(fax_num,3)+"-"+mid(fax_num,4,3)+"-"+right(fax_num,4)
                    See our Hybrid Option here;
                    https://hybridapps.example-software.com/


                    Apologies to anyone I haven't managed to upset yet.
                    You are held in a queue and I will get to you soon.

                    Comment


                      #11
                      Originally posted by Ted Giles View Post
                      Mark, this is the logic for taking a Char field, chopping it up and reassembling it.
                      Taken from the Interactive Window. Copy the text into the I/w and try it out.

                      dim fax as c
                      fax = "1234567890" ' I am presuming that the fax# is stored as a character

                      ?fax
                      = "1234567890" 'to see if the value is populated

                      ? left(fax,3) ' left 3 values. Starts at place 1 and selects 3 characters
                      = "123"

                      ?mid(fax,4,3) ' mid values. Starts at place 4 for 3 characters
                      = "456"

                      ? right(fax,4) ' right values. Reads back 4 characters from the end
                      = "7890"

                      ? left(fax,3)+"-"+mid(fax,4,3)+"-"+right(fax,4) ' Assemble it and add the "-" as a separator. You only need this bit.
                      = "123-456-7890"


                      So in your script, the fax_num to be written might be

                      left(fax_num,3)+"-"+mid(fax_num,4,3)+"-"+right(fax_num,4)
                      Ted,

                      This was incredibly helpful. I was easily able to adapt this logic to my application and it works great.

                      Many thanks!

                      Comment


                        #12
                        Gosh Ted,
                        LOL!! And all these years I've used substr(fax_num,4,3) and I could have used mid(fax_num,4,3). Never too old to learn.
                        Mike W
                        __________________________
                        "I rebel in at least small things to express to the world that I have not completely surrendered"

                        Comment


                          #13
                          Mike, ... but sometimes too old to retain ! (I speak from personal experience.)

                          Comment


                            #14
                            I thought it would be easier to explain;
                            Left Middle Right

                            Substr is quicker to code ( copy and change start and length ) when chopping up a long string.

                            See our Hybrid Option here;
                            https://hybridapps.example-software.com/


                            Apologies to anyone I haven't managed to upset yet.
                            You are held in a queue and I will get to you soon.

                            Comment

                            Working...
                            X