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

Alpha UserName in MS SQL Trigger

  • Filter
  • Time
  • Show
Clear All
new posts

  • Alpha UserName in MS SQL Trigger

    Hello Everyone! This is my first post.

    I am looking into how I will link Alpha to an existing MS SQL 2008 R2 database, specifically how I will need to modify my SQL insert and update triggers in key tables. Presently, I am pulling the username from either the sql authenticated login or the Windows Authenticated login. With my Alpha app, there will be the Alpha username and group info, but the connection to MS SQL will be with a fixed username (i.e. remoteuser) if I understand correctly. Even if/when Windows Authentication is an option, this would only apply to people using my Alpha app on a Windows platform.

    In my SQL insert and update triggers I would like to pull the Alpha UserName if the SQL username is 'remoteuser'. I'm really hoping this is possible as I can't have records list 'remoteuser' as the username of the inserts/updates in my key tables. Of course, I am looking for an efficient solution as these triggers fire regularly.

    Thanks a lot,

  • #2
    Re: Alpha UserName in MS SQL Trigger

    Hi Bruce,
    I have been pondering this also but I suspect it will be impossible.

    We are working on the basis that any Update fields (CreateUser, CreateDate, UpdateUser, UpdateDate) will have to be managed whenever we are updating or creating records. e.g. they are addition fields that we have to populate when we are writing to the tables.

    That being said, I would live to hear from others on this topic. I would love to know if there is a way to get the logged in Alpha user into a SQL table trigger.



    • #3
      Re: Alpha UserName in MS SQL Trigger

      Can you (either of you) describe what you are trying to accomplish?
      Steve Wood
      There is no Cloud. It's just someone else's computer.
      Web - Mobile - Hosting - Products - Frameworks - Developer Resources
      AlphaToGo | IADN (100% Alpha Anywhere Websites)


      • #4
        Re: Alpha UserName in MS SQL Trigger

        Good evening, Steve,

        In many of my MS SQL tables, I have a trigger that fires when a new record is added or when a record is updated. These triggers have code that updates the following fields: CreateUser, CreateDate, UpdateUser, UpdateDate. MS SQL can easily pull the username based on the SQL session login. Triggers are a wonderful to maintain mundane tasks - without having to pass the same variables repeatedly.

        The question is... when connecting from Alpha to MS SQL, how can I obtain the Alpha username as the session login to SQL will be fixed (WebServer login).



        • #5
          Re: Alpha UserName in MS SQL Trigger

          Hi Bruce and Bruce,
          This is how I would go about it:
          Use a session variable to store the Alpha Username.
          When you insert or update a record in the source table - for which you wish to apply the insert or update trigger - use a parametized stored procedure containing the Alpha Username as one of the parameters
          Under the assumption that you are having the CreateUser and UpdateUser as columns in the source table insert / update CreateUser / UpdateUser column with the Alpha Username parameter.
          Then - as part of the trigger t-sql - use the Inserted temporary table - which is an exact copy of the row that has been inserted / updated and thus containing the Alpha Username - as part of your insert / update trigger t-sql to propagate the Alpha Username into whatever other table row you require the Alpha Username…

          ...currently sniffing around to see if Alpha Anywhere should replace MS Access as my next development platform


          • #6
            Re: Alpha UserName in MS SQL Trigger

            Thank you Borge for the comment.

            Sounds like what I was planning to do: if the t-sql trigger sees that the sql session user is WebUser, then don't fire the Username parts of the trigger, but rather have Alpha pass a stored procedure to not only update the regular data, but also the Username with the Alpha Username.

            Come to think about it, better yet would be to have the Alpha Username populate to a (hidden) field in my Alpha form that is bound to the corresponding Username fields in my backend. This would be a one liner just before the data is submitted to the backend. This way the fields will update as a part of the regular update process to the backend. The caveat being that the t-sql trigger not overwrite the newly written Alpha Username with the sql session Username immediately afterward. I'm curious now if I can get this wonderful theory to work!

            Bruce - does this make sense what I am proposing?