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

Security issue, works fine in working preview, but not in localhost

  • Filter
  • Time
  • Show
Clear All
new posts

  • Security issue, works fine in working preview, but not in localhost

    Hi all,

    Created a dialog to enter new users into the security framework and to add the new user info into a MySQL table like on video D_SF_2, when I execute it on working preview all works fine, the new user gets created in both the security framework and my table. But after I publish it to my localhost and run it from there the new user record gets added to the SQL table, but the it is never added to the security framework.

    Seems, curious that I can not find the security tables anywhere either, is the security data actually stored on a DBF table? I am publishing all files, even cleared history just in case. Have always allowed for all pages and components and did publish the security files from the web security component and also added the "New User" group under users and groups.

    Any one have an idea what am I doing wrong?

    Thanks, Juan
    Juan Silva
    My Small Bizz, LLC

  • #2
    Re: Security issue, works fine in working preview, but not in localhost

    Security tables are dbf. There is a way to make them be SQL although it still uses the dbf tables as a pointer. The dbf security tables live in the webroot so they should be there in localhost a5webroot. You are probably looking at your development copy of the security tables which will is necessarily different from the development copy of said tables. In short, it's probably working correctly; you just looked in the wrong place.
    AlphaBase Solutions, LLC


    • #3
      Re: Security issue, works fine in working preview, but not in localhost

      Thank you Peter, that would explain it all, never saw an error happen, even debugged the hell out of it. Too tired to get into that now, but will check it out early in the morning. Would you happen to know the name of the security tables, would they be linked like you would do with any other dbf table? or do I need to take other thinks into consideration?

      Juan Silva
      My Small Bizz, LLC


      • #4
        Re: Security issue, works fine in working preview, but not in localhost

        See attached image...

        web security.gif
        AlphaBase Solutions, LLC


        • #5
          Re: Security issue, works fine in working preview, but not in localhost

          One of these should help.


          • #6
            Re: Security issue, works fine in working preview, but not in localhost

            Thank you all for the help.

            To help the next person I have attached a zip compressed file that includes the Alpha PDF on the subject, a MySQL SQL create table script and the active link tables needed to convert Alpha security from DBF tables to MySQL.

            1. Backup all current websecurity_* files to secure folders, a5webroot and current development area.
            2. extract files on my zip file to a directory
            3. execute the sql script on your database
            4. copy the active link files included to the a5webroot and your project folder

            My final result was that since the new dbf files are links to MySQL, I can test from inside my Alpha 5, or after publishing from any browser that can access my a5webroot application.

            A5 websecurity to

            Note: my project is in the first stages of development so I did not need to transfer any existing users to MySQL tables, read the Alpha documentation attached to do that. I do not make myself responsible of any data loss resulting from advancing your cause.
            Last edited by jmsilva; 07-24-2012, 07:19 PM.
            Juan Silva
            My Small Bizz, LLC