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

Useful Example Using XDialog

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

  • MoGrace
    replied
    Re: Useful Example Using XDialog

    My updated function is now posted here

    Leave a comment:


  • Al Buchholz
    replied
    Re: Useful Example Using XDialog

    Originally posted by Ray in Capetown View Post
    That was Jon Koh, posted his use of the code - nor sharing anything. Don't know what you call that ....so not hijacking, maybe bragging ?
    Or an evolving piece of software.

    Leave a comment:


  • Ray in Capetown
    replied
    Re: Useful Example Using XDialog

    That was Jon Koh, posted his use of the code - nor sharing anything. Don't know what you call that ....so not hijacking, maybe bragging ?

    Leave a comment:


  • Peter.Greulich
    replied
    Re: Useful Example Using XDialog

    Oh yeah, I guess you didn't. I guess I got mixed up.

    Leave a comment:


  • MoGrace
    replied
    Re: Useful Example Using XDialog

    I didn't post a screenshot, and all I did was add some buttons and make it sizeable. If you want to move my posts, that's fine but the initial credit belongs to Chris.

    Leave a comment:


  • Peter.Greulich
    replied
    Re: Useful Example Using XDialog

    Judging by your screen shot you built a completely different product, which is great. But I think it should go in its own thread.

    Leave a comment:


  • MoGrace
    replied
    Re: Useful Example Using XDialog

    But Peter, you were the first to make changes...

    Leave a comment:


  • Peter.Greulich
    replied
    Re: Useful Example Using XDialog

    I think this thread has been hijacked.

    Leave a comment:


  • MoGrace
    replied
    Re: Useful Example Using XDialog

    I'm working on adding a tabbed object so you can see the sets too.

    I put my shared scripts into an aex file and copy that to the addins_installed folder. The original functions in the library file can still be edited and then recompiled.

    Leave a comment:


  • Mike Wilson
    replied
    Re: Useful Example Using XDialog

    Ron,
    I have an separate app I call shared_scripts and I place all my mainstay scripts that I use always, and then it's a simple matter of adding the library of that shared scripts to your current app.

    Leave a comment:


  • Ronald Anusiewicz
    replied
    Re: Useful Example Using XDialog

    Is it possible to store this function in one place so that it's accessible to all work spaces or does the function need to be added to the code tab for each work space?

    Leave a comment:


  • johnkoh
    replied
    Re: Useful Example Using XDialog

    Thank you for sharing. Robin,

    I can make a better on my IDE xdialog with your codes.

    my_A5Ide_Layout.jpg

    Leave a comment:


  • MoGrace
    replied
    Re: Useful Example Using XDialog

    I made some modifications to the original function like adding a few buttons and made the xd sizeable so you could see the calc field rule definitions. Now besides viewing the default browse, you can check the indexes, update them, edit the field rules, pack the table if deleted records are found and even edit the table structure. Also you can save the info to a temp file, preview it and then optionally print it.

    I gave the function a new name so you can import and test it.

    CP_Info_07292016.txt

    Leave a comment:


  • Mike Wilson
    replied
    Re: Useful Example Using XDialog

    I think for developers this is a very sweet function. I added {position=remember} to the body code to get it to open where i want it placed and this is for me now open at all time when I'm developing. Thank guys for this!

    Leave a comment:


  • Lance Gurd
    replied
    Re: Useful Example Using XDialog

    Chris, latest additions really great. But scared me the number of tables that are opened by my main menu which has lots of dockpanels with data driven menus and other information in them. Time for a re-think, I think too much over-head there.

    Leave a comment:

Working...
X