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
Devcon 2020 Goes Virtual! LEARN MORE >

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 Rule Unique Validation is not working

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    Field Rule Unique Validation is not working

    I have a number list--floating point 2 decimal places. I have the field rule validation section set to "unique". Why can I still enter duplicate numbers?

    It did not used to work this way. Any ideas?
    Tags: None
    #2
    RE: Field Rule Unique Validation is not working

    Dennis,

    I'm not sure what's going on in your application, but I have found instances where numeric comparisons fail because of the vagaries of converting numbers from base 10 to base 2. Sometimes it's not even possible for the computer to completely express a base 10 number in binary form. As a result whenever I need to use a "numeric" identifier, but do not expect to be doing any arithmetic with it later on, I store it in a a character type field. I wonder if you'll have better luck if you did the same?

    -- tom

    Comment

      #3
      RE: Field Rule Unique Validation is not working

      Gee, I would think that A5 uses BCD for numbers!

      Comment

        #4
        RE: Field Rule Unique Validation is not working

        Dennis,

        This is a bit beyond my 'comfort zone', but it's my understanding that the original dBase format required all values to be stored in the table as ascii strings, whether the field was char, logical, or numeric. If Alpha Software started storing binary values instead of ascii equivalents, compatibility with the dbase (Foxpro 2.6) format would be lost, I believe.

        -- tom

        Comment

          #5
          RE: Field Rule Unique Validation is not working

          Dennis,

          I must add that the difficulty you're having may or may not be related to the format of the data in your numeric field. Can't tell without more information from you about how you're doing the comparison. My original post was intended to highlight what I thought was odd and not often encountered... the use of a numeric value, with two decimals, as an identifier.

          Here's an example from the interactive editor, showing the kind of thing I had in mind. Assume that the field is Numeric, width = 6, with decimals 2. Assume also the field name is 'amount', and that the value 0.33 is stored there.

          Code:
          tbl = table.open("Students")
tbl.fetch_goto(2)
?tbl.amount
= 0.330000

dim newvalue as N
newvalue = 1 / 3

result = if(tbl.amount = var->newvalue,"Comparison is ok","Comparison failed")

?result
= "Comparison failed"

tbl.close()
          If you're doing arithmetic to compute the new field value and then using the unique field rule to compare that computed value to the value actually stored in each record of the table, something similar might be happening.

          -- tom

          Comment

          Previous template Next
          Working...
          X