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

Problems with websecurity_users.dbf

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

    Problems with websecurity_users.dbf

    I was wanting to make it possible for people to register on my site. And when they registered, I was going to enter the email address, password, and Ulink into the websecurity_users.dbf table. Alpha will not open that table, nor will it let me include it in my database, so I'm having no luck using xbasic to open it for entering data. Any help would be greatly appreciated

    #2
    Re: Problems with websecurity_users.dbf

    Refer to the help document on adding users using a dialog. You cannot (should not) work directly with the websecurity_* files.
    Steve Wood
    See my profile on IADN

    Comment


      #3
      Re: Problems with websecurity_users.dbf

      well the help file was.. a little less helpful than i thought, but i'll figure it out.. However, should I not be able to open websecurity_users.dbf to check and see if my script is adding users or not? Alpha won't recognize it as a table and half the time neither does visual fox pro..

      Comment


        #4
        Re: Problems with websecurity_users.dbf

        and also.. is there anyway to get the ulink field to auto-increment? I want every user to have a different Ulink?

        Comment


          #5
          Re: Problems with websecurity_users.dbf

          Originally posted by audrummer15 View Post
          well the help file was.. a little less helpful than i thought, but i'll figure it out.. However, should I not be able to open websecurity_users.dbf to check and see if my script is adding users or not? Alpha won't recognize it as a table and half the time neither does visual fox pro..
          Why don't you use the freely supplied web app samples that ship with Alpha5? They have functioning examples of this that you just have to copy into your project...

          Comment


            #6
            Re: Problems with websecurity_users.dbf

            Originally posted by NoeticCC View Post
            Why don't you use the freely supplied web app samples that ship with Alpha5? They have functioning examples of this that you just have to copy into your project...
            because I dont like to copy and paste something that i don't fully understand, i rather learn. And my problem isnt adding users to the database.. i was asking if alpha was supposed to be able to read websecurity_users.dbf because mine doesnt

            Comment


              #7
              Re: Problems with websecurity_users.dbf

              A,

              How secure would those tables be if you could access them directly as you want? Nothing I would want to take responsibility for if/when someone decided to take a look and found the way to read passwords and such. Or even to have a user somehow get into them and make a total mess of the security.

              BTW--with a name like A, maybe you're related to e e cummings?? :)
              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


                #8
                Re: Problems with websecurity_users.dbf

                Originally posted by MikeC View Post
                How secure would those tables be if you could access them directly as you want? Nothing I would want to take responsibility for if/when someone decided to take a look and found the way to read passwords and such. Or even to have a user somehow get into them and make a total mess of the security.
                Precisely....

                Comment


                  #9
                  Re: Problems with websecurity_users.dbf

                  websecurity_users.dbf
                  Strange, I have always been able to edit the security files directly,
                  The only restriction being when passwords are encrypted, but there is an ugly workaround with that. Similar to other password encrypt hacks.
                  -
                  Personally I would make my own web security grid control for CRUD security management in this case.

                  Comment


                    #10
                    Re: Problems with websecurity_users.dbf

                    I could comment, but best left obscure. Alpha has talked of plans to encrypt the entire websecurity* tables in the future making them inaccessible other than through their official functions.
                    Steve Wood
                    See my profile on IADN

                    Comment


                      #11
                      Re: Problems with websecurity_users.dbf

                      I would like to see the ability to have security tables inside of SQL Server,
                      without any custom encryption, allowing for simple table edits to create/update users.

                      Thoughts?
                      Frank R

                      Comment

                      Working...
                      X