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

XDialog Box - Set Focus

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

    #16
    Re: XDialog Box - Set Focus

    The XDialog is not close yet.... still open but the field are disable.

    I have created a "Edit" Button for user to click for edit the record, at the time, the field become Enabled and Background become White.. but how to do that. thanks.u

    they want to open the XDialog that all the fields are disable and for view only. If they want to change, then click Edit button follow by submit it. but how do i do that?
    Many Thanks.

    Jack Lim

    Comment


      #17
      Re: XDialog Box - Set Focus

      Depending on what you want, that can get really complicated.

      You can disable a field with the "?" argument but that will also gray it out. That doesn't always look good because it makes things harder to read.

      You can make a field read-only with the "R" directive but doing that after the Submit button is pushed requires actually shutting down the xdialog and automatically restarting it. The user won't be able to see it happen but it take's some complex code to do it. The "R" directive isn't a variable - it's actually hard coded as part of the xdialog text.

      If you really want to do that, I'd start with using the ? argument something like this:

      Set this before starting the xdialog:
      allow_change = .T.

      Then create the xdialog using the allow_change variable to determine whether or not the fields should be enabled:
      [.10ProductID?allow_change]

      Then, in the %code% section, reset the allow_change value whenever appropriate. If all data was entered correctly, set it to .F.. If the user clicks the Edit button, set it back to .T..

      However, I see a lot of potential issues with this. For example, you will have to know if the user is entering a new record or editing an existing record. If they enter a new record and the values remain in the fields, then they click an "Edit" button, how can you know if they want to edit the existing record or start a new record that has many of the same values? Even if you provide two buttons, an Edit and a New Record button, I'd be willing to bet somebody will get confused by what they mean and mess it up.

      This can be done but it will take a lot of checking to make sure the data doesn't get messed up.

      Comment

      Working...
      X