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

Help with field rules

  • Filter
  • Time
  • Show
Clear All
new posts

  • Help with field rules

    I wrote a script to limit the user to the number of times that a demo program could be used before registering.Is it correct to replace the field rules file to enable the program? Should I replace the .DDD .DDM and or .DDX files to allow unlimited program use? Is there any additional re-indexing that needs attention..or just replace the files and let Alpha 5 do its thing??

  • #2
    RE: Help with field rules


    If you have a script that is controlling the number of times a program can be run you must protect the script and the dbf that is used for counting. The user can't get at either one. I would recommend encrypting the fields in the dbf that contains the count. The script must be password protected.

    If the user attempts to modify the dbf the script will not be able to read the data correctly because of the data encryption. If the user looks at the data it would be unreadable.

    When you want to activate the unlimited usage feature you can adjust the control dbf value by accepting a code in your script and modifying the dbf data. this code would be unique to each user.

    Your initial suggestion can also be used but requires much more interaction on the part of the user.

    I hope this helps.

    bob adler


    • #3
      RE: Help with field rules

      Thanks for the tips regarding encryption and password protection. Do you have any references for creating scripts which will accept a code to modify dbf data as you suggested?



      • #4
        RE: Help with field rules

        I wrote a script ... Should I replace the .DDD .DDM and or .DDX files...

        I think I like Bob's idea best but here's some add'l info on script locations:

        If the script is a global script, it is put in the database files themselves (.alb/.alm/.alx) by default. So, unless you have specifically defined them to be stored in one of the tables, you would need to copy the database files in order to give someone the new script.

        If the script is attached directly to a form event, button, or field rule event, that script will be included in the .ddd/.ddm/.ddx files.


        • #5
          RE: Help with field rules

          Thanks for additional ideas on how to solve the problem.
          Still looking for some information that Bob alluded to on how to create a script that will permit the user full useage when a code is entered


          • #6
            RE: Help with field rules


            sorry for the delay.

            Along time ago i rember seeing something on learn alpha about encrypting passwords.

            if my clients give be a breather tonight I will send you my approach to encrypting passwords.

            bob adler