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

Multiple form instances being created with log on/off routine

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

    #16
    Re: Multiple form instances being created with log on/off routine

    Try this.
    I like keeping if-endif tight so sometimes it's best to use does not equal versus equal. And I always have a cancel button on a dialog.

    Code:
    DIM GLOBAL gvModuleName as C
    DIM GLOBAL gvuser as C
    DIM GLOBAL gvEmpName as C
    DIM GLOBAL gvEmpid as C
    DIM GLOBAL gvLogOnOff as C
    
    DIM SHARED vuserpass as C
    DIM SHARED varC_result as C
    DIM SHARED vCenterForm as C
    DIM vuserfound as C
    
    'Change Title to "Log On As" and refresh parent layout
    	gvModuleName = "Log On As"
    
    'Blank the Username and Password
    	gvuser=""
    	vuserpass=""
    
    'Change the Employee Name to "No Employee"
    	gvEmpName="No Employee"
    
    'Set Log_On_Off button text to "Log On"
    	gvLogOnOff = "Log On"
    	Log_On_Off.text = gvLogOnOff
    
    'Refresh Main Menu
    	topparent.Repaint()
    
    '---------------
    Retry_here:
    '---------------
    ok_button_label = "&Log On"
    'cancel_button_label = "&Cancel"
    varC_result = ui_dlg_box("EIM Track",<<%dlg%
    {font=Arial,10}
    {frame=1,1:Enter your Username and Password:}
    {region}
    {lf};
    Username:| [.40gvuser];
    Password:| [%p%.40vuserpass];
    {lf};
    {endregion};
    {lf};
    {region}
    {justify=right}
    <*15=ok_button_label!Log On*?> <Cancel>
    {endregion};
    %dlg%)
    
    If varC_result="Cancel"
         end
    end if
    
    
    
    IF varC_result = "Log On"
    ' Get data from Employee Master file to verify password - make one text string that has both values and then parse it out below
    ' Lookup the records for the matching username and password
    	lres = lookupc("F",alltrim(gvuser),"alltrim(emplognid)+' -- '+alltrim(emppass)",a5.Get_Path()+"\emp.dbf","_emplognid")
    	vuserfound = word(lres,1," -- ")
    	vpassfound = word(lres,2," -- ")
    
    	'Compare user name entered to that in the Employee Master file (found with lookupc above)
    	'Test User Name
    		IF alltrim(lower(gvuser)) <> alltrim(lower(vuserfound))
    		'Name does not matches - try again
    			ui_msg_box("User Name Not Found","The User Name you entered could not be found",UI_STOP_SYMBOL)
    			gvuser = ""
    			vuserpass = ""
    			GOTO Retry_here
    		END IF
    
    	' Test Password
    		IF alltrim(lower(vuserpass)) <> alltrim(lower(vpassfound)) ' Password matches too
    		'Password does not match - try again
    			ui_msg_box("Password Error!","Password entered is incorrect.",UI_STOP_SYMBOL)
    			'Clear vuserpass variable
    			vuserpass = ""
    			GOTO retry_here
    		END IF
    
    	'SUCCESS:  User name and Password match
    		gvuser = alltrim(lower(gvuser))
    		'Clear vuserpass variable
    		vuserpass = ""
    
    		'Set a Global Variable containing the Employees full name
    		gvEmpName = lookupc("F", gvuser, "alltrim(Empfname)+' '+ alltrim(Emplname)", "emp","_Emplognid")
    
    		'Set a Global Variable containing the Employees ID Number
    		gvEmpid = lookupc("F", gvuser, "alltrim(Empid)", "emp","_Emplognid")
    
    		'Set a Global Variable containing the current module name
    		gvModuleName = "Main Menu"
    
    		'Form Name to Center when opening
    		vCenterForm = "Main_Menu"
    
    		'Set Log_On_Off button text to "Log Off"
    		gvLogOnOff = "Log Off"
    		Log_On_Off.text = gvLogOnOff
    
    		if a_form_current<>"Main_Menu"
    			'Close the current form
    			parentform.close(.f.)
    
    			'Loads the Main Menu
    			form.view(vCenterForm, "", "", "center", "center")
    		end if
    
    		'Refresh Main Menu
    		' refresh screen
    		topparent.resynch()
    		topparent.refresh_layout()
    		topparent.Repaint()
    
    END IF
    Mike W
    __________________________
    "I rebel in at least small things to express to the world that I have not completely surrendered"

    Comment


      #17
      Re: Multiple form instances being created with log on/off routine

      This is offered without testing. changes to your existing code are shown in red.


      Code:
      'Close the current form
      'parentform.close(.f.)  [COLOR="Red"] <======= comment out[/COLOR]
      
      'Set a Global Variable containing the Employees full name
      gvEmpName = lookupc("F", gvuser, "alltrim(Empfname)+' '+ alltrim(Emplname)", "emp","_Emplognid")
      
      'Set a Global Variable containing the Employees ID Number
      gvEmpid = lookupc("F", gvuser, "alltrim(Empid)", "emp","_Emplognid")
      
      'Set a Global Variable containing the current module name
      gvModuleName = "Main Menu"
      
      'Form Name to Center when opening
      vCenterForm = "Main_Menu"
      
      'Set Log_On_Off button text to "Log Off"
      gvLogOnOff = "Log Off"
      Log_On_Off.text = gvLogOnOff
      
      'Loads the Main Menu [COLOR="red"]if not on the Main menu itself[/COLOR]
      [COLOR="red"]v_curr_form_name = parentform.name()
      if v_curr_form_name <> "Main_menu" then
           parentform.close(.f.)
           form.view(vCenterForm, "", "", "center", "center")
      end if[/COLOR]
      
      'Refresh Main Menu
      topparent.Repaint()

      Comment


        #18
        Re: Multiple form instances being created with log on/off routine

        Tom and Mike,

        Thank-you both. The code I ended up using is below.

        I am curious what is the advantage of using a_form_current vs. parentform.name()?

        Comment


          #19
          Re: Multiple form instances being created with log on/off routine

          Another question, that may or may not be related. When I am on the Main_Menu form and run the Logon script (Which is now working), the control panel opens, even though it was previously hidden via ......controlpanel.hide() in the Autoexec script. Based on the code you have worked on what causes the Control panel to open again? What is the best way to close it again in the script above?

          Comment


            #20
            Re: Multiple form instances being created with log on/off routine

            I don't see anything in either code that would show a hidden control panel. Does it happen no matter what form you are on?
            Mike W
            __________________________
            "I rebel in at least small things to express to the world that I have not completely surrendered"

            Comment


              #21
              Re: Multiple form instances being created with log on/off routine

              ok_button_label = "&Log On"

              is not what you are testing for here:

              IF varC_result = "Log On"

              Try:

              IF varC_result = "&Log On"
              Robin

              Discernment is not needed in things that differ, but in those things that appear to be the same. - Miles Sanford

              Comment


                #22
                Re: Multiple form instances being created with log on/off routine

                Originally posted by MoGrace View Post
                ok_button_label = "&Log On"

                is not what you are testing for here:

                IF varC_result = "Log On"

                Try:

                IF varC_result = "&Log On"
                I am new to Alpha scripting so my understanding may be flawed but here goes....

                "&Log On" is the button's label and the IF statement is checking for the result of the dialog box "ui_dlg_box" and not the buttons label.

                Does that sound correct?

                Comment


                  #23
                  Re: Multiple form instances being created with log on/off routine

                  Scott,
                  Don't get too distracted by what Robin wrote. Maybe she can explain what issue that might relate to because I'm not seeing it applies to your issue.
                  Mike W
                  __________________________
                  "I rebel in at least small things to express to the world that I have not completely surrendered"

                  Comment


                    #24
                    Re: Multiple form instances being created with log on/off routine

                    Originally posted by Mike Wilson View Post
                    Scott,
                    Don't get too distracted by what Robin wrote. Maybe she can explain what issue that might relate to because I'm not seeing it applies to your issue.
                    Absolutely none since I didn't see that the change event was the same name!
                    Robin

                    Discernment is not needed in things that differ, but in those things that appear to be the same. - Miles Sanford

                    Comment

                    Working...
                    X