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 MS SQL INSERT Stored Procedure

  • Filter
  • Time
  • Show
Clear All
new posts

  • Help with MS SQL INSERT Stored Procedure

    Hey All,

    I have been wracking my head with this one. I would like to use a SP for security reasons but I can't get this thing to run! The full SQL statement below works but the SP won't execute without error. I get a .F. on the flag but 'Success' in my call result text.

    	Dim conn  as SQL::Connection
    	Dim argz as SQL::Arguments
    	Dim SQL as c 
    	Dim SQLStatement as c
    	dim cLoginType as c = ""
    	dim cResultText as c
    	'flag to test if connection opens
    	dim flag as l
    	SQLStatement = <<%sql%
    	INSERT INTO WebUsersLogins (Username, IPaddress, LoginError, LoginType) OUTPUT INSERTED.Id VALUES('test3','1001001003','gridinitialize3','in')
    	SQL = <<%sql%
    	EXEC jwspWebUsersLoginsInsert(:username,:ip,:loginerror,:logintype)
    	cResultText = conn.CallResult.Text							
    	'flag = conn.execute(SQLStatement)
    	flag = conn.execute(SQL,argz)
    Use RaTSTest
    ALTER PROCEDURE jwspWebUsersLoginsInsert 
    @username nvarchar(250), @ip nvarchar(50), @error nvarchar(250), @logintype nvarchar(3) 
    /*This procedure adds a record everytime a user logs in to the Reportal and is called by the Web User Security function 'saveLoginLog' */
    INSERT INTO WebUsersLogins (Username, IPaddress, LoginError, LoginType) 
    VALUES(@username, @ip, @error, @logintype);

  • #2
    Re: Help with MS SQL INSERT Stored Procedure

    EXEC jwspWebUsersLoginsInsert(:username,:ip,:loginerror,:logintype)
    Have you tried replacing the above with

    EXEC jwspWebUsersLoginsInsert @username = :username,@ip = :ip, @error = :loginerror, @logintype = :logintype
    Glen Schild

    My Blog


    • #3
      Re: Help with MS SQL INSERT Stored Procedure

      Hi Joseph,

      It doesn't look like you executed the procedure. This is clunky, but it works for me. :)

      dim cn as sql::connection"::Name::xxx")

      dim flag as l
      flag = cn.Execute("exec fnow_edit_attendance @pactionid=:pactionid, @pactivityid=:pactivityid," + \
      "@pactivitydetailid=:pactivitydetailid, @pdos=:pdos, @pstarttime=:pstarttime, @pendtime=:pendtime, @pduration=:pduration," +\
      "@pgroupsize=:pgroupsize, @plocation=:plocation, @prate=:prate, @punits=:punits, " +\
      "@ptotalamt=:ptotal_amt, @preturn_message=:preturn_message",args)
      if cn.CallResult.text <> "Success" then
      on_validate.hasError = .t.
      on_validate.errortext = "Server error reported was: " + cn.CallResult.text
      end if


      • #4
        Re: Help with MS SQL INSERT Stored Procedure

        Thanks! Got it working! I had a syntax error. I don't know why I thought I needed parenthesis around the parameters, but I think that was the issue.

        I didn't need to do
        mySProc @parameter = :argument
        because I was passing all the parameters in the same order as listed in the SP and could just do
        mySProc :arguments
        but obviously that isn't the case in every scenario

        Thanks for the help!


        • #5
          Re: Help with MS SQL INSERT Stored Procedure

          Glad you got it to work, I must admit I have got into the habit of expressly naming the parameters as it helps when debugging and future reference.
          Glen Schild

          My Blog