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

Replacing V7 login with V8 web security. Procedure?

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

    Replacing V7 login with V8 web security. Procedure?

    A little advice on correct procedure required to try to ensure that I don't corrupt an existing working web application.

    I currently have a V7 login created by copying the tutorials. The web is functioning well and being used by my clients.
    However I wish to adopt the new functionality in V8 to create a more flexible web security login and want to ensure that all traces of the old system are removed.

    Could someone please advise on the procedure required to change over - for example is the logintest automatically created when setting up new web security, is the additional code to each page automatically created etc.

    Just a little guidance required.

    Regards Robert

    #2
    Re: Replacing V7 login with V8 web security. Procedure?

    Unfortunately it is far from that easy and I doubt anyone could provide a 'little guidance' that would get you anywhere, its just become a lot more complicated than that.

    If you can wait another week, I am releasing a complete Login and User Management module for V8. This will be like my other "drop-in" modules on my website. Only, I can't make this one completely programming-free, there will be some programming because every instance is a little different.

    The major difference between V7 and V8 in terms of login, security is that V8 has hidden tables used to maintain security information. They are't really hidden, but you are not allowed to access or manipulate them. Those tables hold the minimim required information to maintain security. So, you then have to maintain TWO user tables, the hidden one with login info, and your own Users table with things like Name, Address, etc.

    What I have put together uses all of the security framework functions plus regular functions into a neat package that allows management of those two worlds, simultaneously and transparently. Difficult because you have to either guarantee those two tables remain completely in sync, or you have to provide functions to put them back in sync. I think I've perfected the first part, but have added the second part also.

    What I am working on now are 'bulk' actions, so you can import (and export) user information and properly process them through the security model. You can do some of these bulk actions if you involve the desktop authoring computer, but I believe web apps must be entirely self-contained and not rely on a client computer for modification (at least of things like user information).

    In response to your last paragraph, there is no logintest and no code on any page in the new security model.
    Steve Wood
    See my profile on IADN

    Comment


      #3
      Re: Replacing V7 login with V8 web security. Procedure?

      Robert,

      I've created apps both ways, by converting a version 7 app and by creating a version 8 app from scratch. I can tell you that it takes about as long to convert as to create an app from scratch.

      I like the new security system and wouldn't go back, but if I was thinking about updateing an old app, I wouldn't try to convert, I would start from scratch and rebuild my application from the beginning with the new security. It uses security groups rather than the old security levels, and that takes a different mindset.

      So, my recommendation is upgrade to version 8, but if you want to use the new security, create a version 2 of your app from sctratch using it. You'll also appreciate the other features of version 8 by doing it this way such as the multicolumn formatting and the show hide features.

      Pat
      Pat Bremkamp
      MindKicks Consulting

      Comment


        #4
        Re: Replacing V7 login with V8 web security. Procedure?

        Thank you Steve and Pat for your input. I had a sneeking suspicion that it wouldn't be staightforwad but didn't realise that it would be that complicated. I'll just hangfire for a little while and hope that the work that Steve is progressing will help me on my way.

        Thank you both
        regards Robert

        Comment

        Working...
        X