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

buttons don't work after moving from v8->v9

  • Filter
  • Time
  • Show
Clear All
new posts

  • buttons don't work after moving from v8->v9

    Title should read "Buttons don't work:)"

    When i moved my db from v8 to v9 some of my buttons quit working.

    The buttons use action scripting to open other forms. I have one form where 6 buttons are now not working.

    Here is the xbasic for the action scripts on one button:
    '*******************************this part is in an inline xbasic action script
    dim global name as c
    name =  topparent:full_name.value
    '************************************this part is an action script
    'Check to see if you are running the script from within a Form
    dim flag_error as l
    flag_error = .f.
    if is_object(topparent.this) then 
    	p = topparent.this
    	if eval_valid("P:Client_id.value") then 
    		DELETE Parameter1 
    		'Set the Parameter variable to the object's .value property
    		Parameter1 = eval("P:Client_id.value")
    		flag_error = .t.
    	end if 
    	flag_error = .t.
    end if 
    if flag_error then 
    	ui_msg_box("Error","Client_id does not exist. This script cannot be run in this context.",UI_STOP_SYMBOL)
    end if 
    filter = "Client_id = [varC->parameter1]"
    query.filter = replace_parameters(filter,local_variables())
    query.order = ""
    'Open the layout_type showing just the records that satisfy the filter
    DIM Shared varP_Bodyfat as P
    DIM layout_name as c 
    layout_name = "height"
    varP_Bodyfat = :Form.viewqueried(layout_name,query.filter, query.order ,"dialog","Center","Center")
    'After the user closes the dialog form, the form remains in memory and the script 					
    'continues with the next command.																													
    'You can insert any code here that you want to execute before the dialog form (which is now			
    'hidden) is removed from memory with the .close() command. 											
    'The code that you insert here can refer to the form using the pointer variable, varP_Bodyfat	
    if is_object(varP_Bodyfat) = .t. then 																									
    end if
    Since it is action scripting and not 'home made" xbasic I do not see why it does not work in v9 but is fine in v8.
    Thanks for the help
    Last edited by reynolditpi; 03-29-2008, 09:50 AM. Reason: I cannot spell!

  • #2
    Re: buttons to work after moving from v8->v9

    Here is another code that is not working:

    dim global new_image as c
    dim global client_id as c
    client_id = topparent:client_id.value
    new_image = topparent:image1.value
    DIM Shared varP_Add_Image as P
    DIM layout_name as c 
    layout_name = "Add Image"
    varP_Add_Image = :Form.load(layout_name,"dialog","","Center","Center")
    This is from an action script as well.


    • #3
      Re: buttons to work after moving from v8->v9

      What happens? Do you get an error, or does nothing happen?

      The code in your example is pretty simple. You can go to the interactive window in alphasports and test simplar code. On my machine, this works fine. Does it work on your?

      p = form.load("Edit_Customer_Info","dialog","","center","center")


      • #4
        Re: buttons to work after moving from v8->v9

        In v9 it did nothing. in v8 it worked form.

        I deleted the action scripts that were not working and replaced them with some custom xbasic and it works.



        • #5
          Re: buttons to work after moving from v8->v9

          I have the same problem with a button on my for that was created in v8 to open another form.When I press the button in version 9 I get the fly over effect when the mouse passes over and a brief hourglass when pressed and then nothing. It still works in version 8.
          The button was created with action scripting "open form"
          I have uploaded the database.
          look at the "View/Edit Selected jobsheet" Button

          From the Main Menu Press button View customerjobsheet information
          then go to the jobsheet summary "Tab"
          select a jobsheet from the browse and then press the "View/Edit Selected jobsheet".
          Must have something to do with the browse?


          • #6
            Re: buttons to work after moving from v8->v9

            Sounds very similar.


            • #7
              Re: buttons to work after moving from v8->v9

              Thanks for the sample database.

              I was able to duplicate the problem. It is fixed now. I will put out an update tomorrow morning.

              there was a typo in some code in form.viewQueried() that would cause it to fail if using V9 and if the form was based on a set. if the form is based on a table, then .viewQueried() is working fine.