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

Help understanding xbasic error

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

    Help understanding xbasic error

    Web app. 4642-4981.

    When a user logs out they are redirected to my logout.a5w page. In that page is the code you see below. This works most of the time. On occasion, however, the user will get a 500 error. Also below is the error from the log. So, what is going on here? Is there something I need to improve upon?

    Code:
    dim xb as p
        xb = require("user_tracker")
    dim pUser as p
    
    a5ws_logged_in_user_values(pUser)
    		
    dim userid as c = pUser.userId
    dim clientid as c = session.__protected__clientid
    dim whatTask as c = "Logout. User: " + pUser.userId
    dim whatPage as c = "Logout Page"
    dim oldvalue as c = "N/A"
    dim newValue as c = "N/A"
    	
    xb = xb.user_tracker(pUser.userId,clientid,whatTask,whatPage,oldvalue,newValue)
    
    a5ws_logoutuser()
    
    response.redirect("login.a5w")
    Error message from logs...

    Mon Feb 5 10:03:30 2018
    Thread: AppServerWorker8
    Request URI: /logout.a5w
    Script: " /logout.a5w"
    Line: 19
    xb = xb.user_tracker(pUser.userId,clientid,whatTask,whatPage,oldvalue,newValue)
    Variable type mismatch: Cannot assign data of type 'C' to variable of type 'P'.
    Execution Stack:
    0#1 evaluate_shared_private(
    0#39 OOhttpdServerClientMIME(ptemp,"AppServerMain")
    0#2 A5WCallResult = evaluate_a5w_to_response(page_contents,Response,quote(" " + eval_settings.global.Request.ScriptName),eval_settings,EVALUATE_A5W_TIMEOUT,RequestBundle.RequestInfo.Filename.Path)
    0#19 xb = xb.user_tracker(pUser.userId,clientid,whatTask,whatPage,oldvalue,newValue)
    Mike Brown - Contact Me
    Programmatic Technologies, LLC
    Programmatic-Technologies.com
    Independent Developer & Consultant​​

    #2
    Re: Help understanding xbasic error

    Hi Mike,
    It would appear your code is ok from what you have posted.
    It also appears the error is coming from the function xb.user_tracker(). Can you post that?

    Just a question? In the first part of your code you have:

    dim pUser as p
    a5ws_logged_in_user_values(pUser)
    dim userid as c = pUser.userId

    Can you use this command to get the userid? userid = a5ws_getcurrentuser()
    Mike Reed
    Phoenix, AZ

    Comment


      #3
      Re: Help understanding xbasic error

      Originally posted by Mike Reed View Post
      Just a question? In the first part of your code you have:

      dim pUser as p
      a5ws_logged_in_user_values(pUser)
      dim userid as c = pUser.userId

      Can you use this command to get the userid? userid = a5ws_getcurrentuser()
      The code, as is, works the vast majority of the time. I know it could use some cleaning up. But to do that would be a lot of work as I track numerous operations all over my app.

      The module itself is working correctly. Below is the code in that module. You can see I have some custom error logging in there. That never comes up. My SQL handling module is also working correctly (mbSQL).

      Code:
      function user_tracker as c (userid as c, clientid as c, whatTask as c, whatPage as c, oldValue as c, newValue as c)
      
      	dim xb as p
      		xb = require("mbSQL")
      	dim p as p
      	dim sql as c
      		sql=<<%str%
      		EXEC sp_User_Tracker :userid,:clientid,:whatTask,:whatPage,:oldValue,:newValue%str%
      	dim args as sql::Arguments
      
      	args.set("userid",userid)
      	args.set("clientid",clientid)
      	args.set("whatTask",whatTask)
      	args.set("whatPage",whatPage)
      	args.set("oldValue",oldValue)
      	args.set("newValue",newValue)
      	
      	p = xb.mbSQL("sql",sql,args,"User Tracking","rs",.f.)
      		
      		if p.hasError
      			e.fatalError = .t.
      			file.append("c:\debugData\Xbasic_Module_Error_Log.txt",now() + "   Module Error - Module Name: user_tracker - Details: SQL at line 26 had a problem" + crlf())
      		end if
      
      end function
      exports.user_tracker = user_tracker
      Mike Brown - Contact Me
      Programmatic Technologies, LLC
      Programmatic-Technologies.com
      Independent Developer & Consultant​​

      Comment


        #4
        Re: Help understanding xbasic error

        The web/mobile side is definitely outside my area but an xbasic function, in general, has to have its return value assigned inside the function. I don't see that in yours.

        Code:
        function user_tracker as c (userid as c, clientid as c, whatTask as c, whatPage as c, oldValue as c, newValue as c)
               [COLOR="#FF0000"] user_tracker = <some default value to return if the function does not finish>[/COLOR]
        	dim xb as p
        		xb = require("mbSQL")
        	dim p as p
        	dim sql as c
        		sql=<<%str%
        		EXEC sp_User_Tracker :userid,:clientid,:whatTask,:whatPage,:oldValue,:newValue%str%
        	dim args as sql::Arguments
        
        	args.set("userid",userid)
        	args.set("clientid",clientid)
        	args.set("whatTask",whatTask)
        	args.set("whatPage",whatPage)
        	args.set("oldValue",oldValue)
        	args.set("newValue",newValue)
        	
        	p = xb.mbSQL("sql",sql,args,"User Tracking","rs",.f.)
        		
        		if p.hasError
        			e.fatalError = .t.
        			file.append("c:\debugData\Xbasic_Module_Error_Log.txt",now() + "   Module Error - Module Name: user_tracker - Details: SQL at line 26 had a problem" + crlf())
        		end if
                 [COLOR="#FF0000"]user_tracker = <value to return if the function does finish>[/COLOR]
        end function
        exports.user_tracker = user_tracker
        Apologies if this is not the case where you are working.
        There can be only one.

        Comment


          #5
          Re: Help understanding xbasic error

          Thank you but not the case. I don't need to return anything. The module is simply executing some SQL. That part is working correctly.

          Variable type mismatch: Cannot assign data of type 'C' to variable of type 'P'. is puzzling ... I'm not doing anything else on my logout.a5w other than what I posted above. If the code was bad to begin with I'd expect it to never work. But, again, it works most every time.
          Mike Brown - Contact Me
          Programmatic Technologies, LLC
          Programmatic-Technologies.com
          Independent Developer & Consultant​​

          Comment


            #6
            Re: Help understanding xbasic error

            I was confused by the line

            exports.user_tracker = user_tracker

            which seems to assign the return value of the function to another variable.

            Your user_tracker() function declares and populates two pointer variables.

            dim xb as p
            dim p as p

            xb is populated with xb = require("mbSQL")
            p with p = xb.mbSQL("sql",sql,args,"User Tracking","rs",.f.)

            It would seem the error message is saying that the result of one or the other of the functions called in those assignment is failing to return a pointer, sometimes. Perhaps troubleshooting them is the answer? More precisely, can either of those fail to return a value?
            Last edited by Stan Mathews; 02-07-2018, 04:31 PM.
            There can be only one.

            Comment


              #7
              Re: Help understanding xbasic error

              If my p variable, executing SQL via mbSQL module, had an issue I'd get an error in my custom error tracking...fileappend(). But I'm not getting any errors from there.

              Code:
              p = xb.mbSQL("sql",sql,args,"User Tracking","rs",.f.)
              		
              		if p.hasError
              			e.fatalError = .t.
              			file.append("c:\debugData\Xbasic_Module_Error_Log.txt",now() + "   Module Error - Module Name: user_tracker - Details: SQL at line 26 had a problem" + crlf())
              		end if
              Mike Brown - Contact Me
              Programmatic Technologies, LLC
              Programmatic-Technologies.com
              Independent Developer & Consultant​​

              Comment


                #8
                Re: Help understanding xbasic error

                If you're not tired of my meddling....

                Try it changing

                xb = xb.user_tracker(pUser.userId,clientid,whatTask,whatPage,oldvalue,newValue)

                to simply

                xb.user_tracker(pUser.userId,clientid,whatTask,whatPage,oldvalue,newValue)
                Last edited by Stan Mathews; 02-08-2018, 05:15 PM.
                There can be only one.

                Comment


                  #9
                  Re: Help understanding xbasic error

                  The function works like that. But it works the other way too (most of the time). I suppose I can try this and see if I get anymore errors. Doesn't explain why the error is happening in the first place and why it only happens occasionally.
                  Mike Brown - Contact Me
                  Programmatic Technologies, LLC
                  Programmatic-Technologies.com
                  Independent Developer & Consultant​​

                  Comment


                    #10
                    Re: Help understanding xbasic error

                    ok, I think I'm getting it now. Since I don't need to return anything from my user_tracker module I should just use xb.user_tracker(pUser.userId,clientid,whatTask,whatPage,oldvalue,newValue). For instances where I need to return something I should probably use a separate pointer variable to execute the module like I do with p = xb.mbSQL("sql",sql,args,"User Tracking","rs",.f.).
                    Mike Brown - Contact Me
                    Programmatic Technologies, LLC
                    Programmatic-Technologies.com
                    Independent Developer & Consultant​​

                    Comment


                      #11
                      Re: Help understanding xbasic error

                      For instances where you do need to return something you should assign it to a variable of the proper data type. IOW, if you return a numeric value, you wouldn't assign it to a pointer variable, etc.

                      I was advised, years ago, that a user defined function should always return some value. If the UDF performs an action where a returned value is not needed then it can be defined to return a logical. That logical can be tested to verify that the function finished executing.

                      Code:
                      FUNCTION add_to_pss AS L ( )
                      add_to_pss = .F.
                      'code to do something here
                      add_to_pss = .T.
                      END FUNCTION
                      The function can then be called like

                      Code:
                      if add_to_pss()
                      'function finished ok
                      else
                      msgbox("add_to_pss did not complete normally")
                      end if
                      Last edited by Stan Mathews; 02-09-2018, 05:22 PM.
                      There can be only one.

                      Comment

                      Working...
                      X