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



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

Creating Field Rules in XBasic

  • Filter
  • Time
  • Show
Clear All
new posts

  • Creating Field Rules in XBasic

    i see where i can create/change the easy ones...

    how/where do i get information to access the properties of a lookup field rule?

    i want to require that "field1" exist in table 2 and then use table2 to put a value into "field2".

    i've got this so far:
    dim tbl as P
    dim fr as P
    tbl ="TrashPmt")
    fr = tbl.rules_get()
    ? fr
    V Change_Begin() 'Begin changes to the field rules.
    V Change_End([L Commit]) 'End changes to the field rules.
    Field_Rule_Get as P(fieldName as c[,variableFrame as p]) 'Get (or add) a rule for a field - includes variables of calc fields.
    Field_Rule_Get as P(fieldName as c[,variableFrame as p]) 'Get (or add) a rule for a field - includes variables of calc fields.
    = "Rule.Lookup"
    = "Rule.Unique"
    = "None"
    = "Rule.Validation.List"

    i think the appropriate question is:
    how do i get access to the "Rule.Lookup" class?

  • #2
    Re: Creating Field Rules in XBasic

    I believe the table lookup field rule is essentially a black box, the inner workings of which have not been exposed for us.

    Instead of trying to modify the built in lookup, why not build your own?


    • #3
      Re: Creating Field Rules in XBasic

      Originally posted by Tom Cone Jr View Post
      I believe the table lookup field rule is essentially a black box, the inner workings of which have not been exposed for us.

      Instead of trying to modify the built in lookup, why not build your own?

      i'm willing to build my own; in fact that was what i was starting to do but didn't know what "object values" i needed to "set"...

      in other words, keep talking - i'm listening attentively!!!


      • #4
        Re: Creating Field Rules in XBasic

        Ok. First, write down the specific sequence you'd want Alpha Five to follow, using the smallest possible steps. When I do this I try to think of the specific steps I'd have to take to do it by hand. Let us see what you come up with. We'll offer suggestions. Don't worry about "how" to do it. Concentrate on "what" needs to be done.

        Then think carefully about the context in which the desired sequence should run. We need to find the right "event" to trigger the script. Might be as simple as a button push, but it may be something you'd want to happen automatically. Don't know yet.


        • #5
          Re: Creating Field Rules in XBasic

          after 2 hours of documenting, i realized that it didn't matter because i'd have to define/create a custom browse toolbar which would post the contents of this "trash" file and the custom toolbar i am building for another process does not like to post the data on the browse. that's another topic i'll post shortly after i get it documented sufficiently.

          so, long story made short - i'll have to have a permanent table. and it'll have permanent (manually entered) field rules..

          thanks anyway..............