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

v9 bugs forcing me to v10

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

    v9 bugs forcing me to v10

    I have an application I have been developing in v9, but now I am forced into v10 because of v9 bugs. I really wanted to be able to use a v9 unlimited runtime license and am a bit burned that I can't because of bugs in v9. Two bugs...
    1) Calculated field rules recalculate with table change event. A unique record id value on record entry based on rand() and rand_string() changes when a readdress to the table with a change occurs.
    2) file_is_open() registers as .t. when file is not open but file attribute is read-only. Can't check for file being open. Pretty central in a document control application. I checked v7, v8, and v10 and all but v9 are OK with this.

    Mike W
    __________________________
    "I rebel in at least small things to express to the world that I have not completely surrendered"

    #2
    Re: v9 bugs forcing me to v10

    Good luck with version 10. I hope it is Bug Free.

    Ken

    Comment


      #3
      Re: v9 bugs forcing me to v10

      Actually, my initial testing was wrong. The file_is_open() in v10 also registers a file with file attribute read only as being open. Dunno what to do now....
      Mike W
      __________________________
      "I rebel in at least small things to express to the world that I have not completely surrendered"

      Comment


        #4
        Re: v9 bugs forcing me to v10

        Mike....perhaps as a work-around you could change the file's read only attribute (and then back if necessary) when doing your check? Programmatically of course, not manually (although that would work also!! :D )
        Mike
        __________________________________________
        It is only when we forget all our learning that we begin to know.
        It's not what you look at that matters, it's what you see.
        Henry David Thoreau
        __________________________________________



        Comment


          #5
          Re: v9 bugs forcing me to v10

          Originally posted by Mike Wilson View Post
          A unique record id value on record entry based on rand() and rand_string() changes when a readdress to the table with a change occurs.
          1-Random is NOT unique. You need to rethink this approach, too dangerous.
          2-Automatic recalculation with OnChange event is what should and what is expected to happen. You need to rethink this one as well. An ID field should NEVER be a calc field. Perhaps a default value, but NOT a calc field.

          Comment


            #6
            Re: v9 bugs forcing me to v10

            G,
            Isn't "never" a pretty confining term? I think one exception I can think of right away is a concatenation of fields that when together are unique either due to one, the other, or both being unique or by some definition of how they are derived that when combined they are unique....and a concatenation is a calculated field.....just not probably as what Mike is using but still. . . .

            My point is the generalization I guess. But even though I disagree with this minor point, I do agree (not that my opinion matters all that much!!! :) ) that any field that can be changed, either intentionally or by Alpha inadvertantly, should not be used as an ID or linking field.
            Mike
            __________________________________________
            It is only when we forget all our learning that we begin to know.
            It's not what you look at that matters, it's what you see.
            Henry David Thoreau
            __________________________________________



            Comment


              #7
              Re: v9 bugs forcing me to v10

              if (id="", <calc id>,id)

              that keeps the value if it already exists and puts a value in the field if the field is blank.
              Al Buchholz
              Bookwood Systems, LTD
              Weekly QReportBuilder Webinars Thursday 1 pm CST

              Occam's Razor - KISS
              Normalize till it hurts - De-normalize till it works.
              Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
              When we triage a problem it is much easier to read sample systems than to read a mind.
              "Make it as simple as possible, but not simpler."
              Albert Einstein

              http://www.iadn.com/images/media/iadn_member.png

              Comment


                #8
                Re: v9 bugs forcing me to v10

                Originally posted by MikeC View Post
                G,
                Isn't "never" a pretty confining term?
                Yes.. but when it comes to ID's, I am going for maximum solitary confinement, no exceptions, no mercy, no appeals, no concessions, no commutation, concatenated field or otherwise, sorry NEVER a calc field for an ID, an affixed value as a product of a calculation perhaps but NOT a calc field, never ever.

                I am sorry if my limited vocabulary doesn't allow me to be more affirmative.

                Comment


                  #9
                  Re: v9 bugs forcing me to v10

                  Originally posted by MikeC View Post
                  Mike....perhaps as a work-around you could change the file's read only attribute (and then back if necessary) when doing your check? Programmatically of course, not manually (although that would work also!! :D )
                  Well shiver me timbers, Mike! I assumed you can't change the attributes of an open file, but in trying to prove this... I just proved my contention incorrect. While logical.... it's just not the case, thankfully so. Very cool.... I was fretting, because I didn't have another option. I'm back in business.

                  As for the unique thing.... I gotcha guys... not assured as unique. I'm working to log events in the application and wanted an event id. Over the course of the application lifetime, I'm calculating there will be 50,000 events. I'm thinking this calculation will yield a value unlikely to be duplicated. And I'm willing to bet the goat on it!!!


                  Code:
                  ? padl(remspecial(str(rand()*10000)),4,"0")+rand_string(4)+padl(remspecial(str(rand()*10000)),4,"0")+rand_string(4)
                  = "4313ebpw7440mpps"
                  Last edited by Mike Wilson; 04-17-2010, 02:05 AM.
                  Mike W
                  __________________________
                  "I rebel in at least small things to express to the world that I have not completely surrendered"

                  Comment


                    #10
                    Re: v9 bugs forcing me to v10

                    So Mike, it sounds like this will allow you to use file_is_open() successfully? Always nice to have fairly easy work-around if so.
                    Mike
                    __________________________________________
                    It is only when we forget all our learning that we begin to know.
                    It's not what you look at that matters, it's what you see.
                    Henry David Thoreau
                    __________________________________________



                    Comment


                      #11
                      Re: v9 bugs forcing me to v10

                      If you want a totally unique id, why not use api_uuidcreate()?
                      Peter
                      AlphaBase Solutions, LLC

                      [email protected]
                      https://www.alphabasesolutions.com


                      Comment


                        #12
                        Re: v9 bugs forcing me to v10

                        Hi Peter,
                        Thanks for that. I looked for that... couldn't remember what is was named. Just the uu part. I searched uu*** back and forth and couldn't find it. 'Unique value' didn't find it. What I came up with I was confident would serve the need. So now I'm refreshed... api_uu.....
                        Mike W
                        __________________________
                        "I rebel in at least small things to express to the world that I have not completely surrendered"

                        Comment


                          #13
                          Re: v9 bugs forcing me to v10

                          I commonly use these two calculated field values to get a unique id for a table. The values are 32 and 20 in length, respectively. For normal user activity, the second one is unique without the rand string, but it makes me feel better to add it. They work from the web as well.

                          if(id="",remspecial(api_uuidcreate()),id)

                          if(id="",time("MMddyyyy0h0m0s3")+rand_string(3),id)

                          Random values alone are guaranteed to eventually have a duplicate value.
                          Steve Wood
                          See my profile on IADN

                          Comment

                          Working...
                          X