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

Some ideas please

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

    Some ideas please

    I built a Inventory and maintenance db some time ago in Lotus approach - It has worked very well, but it is now a very old program and does not match some of the enhancements built into Alpha 5. As the user likes the way the program works, they would like it be duplicated with minmum changes to the process if they are going to move to Alpha.

    In doing the duplication I have one set of steps that I am finding little ability to duplicate. Basically it is my create workoder process. I can duplicate most of the steps except the last. What I need to be able to do is put a blank listview on an xdialog and then while the xdialog is open add from another xdialog parts to the listview on the first xdialog.

    I created a movie of the steps with me trying explain what gets done. Sound is poor but I think you can see what I need to do from it. If you go to http://www.onestopsolutions.biz/demo/

    the key to the process is that creates mulitple workorders and therefor all steps need to match this. I can duplicate all but this last step. I am looking for ways to achieve this process. It actually is one that user really likes and would not like to see it change. If there is another way that can be considered with no real problem to the workflow then I am onto a winner as well.
    -----------------------------------------------
    Regards
    Mark Pearson
    [email protected]
    Youtube channel
    Website

    #2
    Re: Some ideas please

    Hi Mark,

    Here is some code from leaning XDialog. It sort of does what you want, but does need some work to do exactly the same as your video.

    Code:
    'Date Created: 12-Jun-2002 08:02:48 AM
    'Last Updated: 12-Jun-2002 08:02:48 AM
    'Created By  : Selwyn
    'Updated By  : Selwyn
    colors = "Red,Green,Yellow,Blue,Purple,Orange,Lime,Cyan"
    colors = stritran(colors,",",crlf())
    dim a_colors[20] as c
    a_colors.initialize(colors)
    dim a_selected[20] as c
    
    ui_dlg_box("Check Box-List Box",<<%dlg%
    {frame=1,1}
    {region}
    This control uses the '^$' directive.;
    [.25,10color1_selected^$colors];
    {lf};
    Value of check box-list box variable:;
    [.25color1_selected];
    {endregion}|
    {frame=1,1}
    {region}
    This control uses the '^$$' directive.;
    [.25,10color2_selected^$$colors!select_color];
    {lf};
    Value of check box-list box variable:;
    [.25,10colorname^#a_selected];
    {endregion}
    %dlg%,<<%code%
    if a_dlg_button = "select_color" then
    	a_dlg_button = ""
    	a_selected.clear()
    	a_selected.initialize(color2_selected)
    end if
    %code%)
    Regards
    Keith Hubert
    Alpha Guild Member
    London.
    KHDB Management Systems
    Skype = keith.hubert


    For your day-to-day Needs, you Need an Alpha Database!

    Comment


      #3
      Re: Some ideas please

      Thanks Kieth, I thought I had asked something too complex, so I appreciate that you took the time to do some research for me.

      Had the same idea as you and checked the learn xdialog, It wasn't until I looked at the Listview under what's new in V10, that it all started to click together. As a result I now get it to do want I want. As per my demo, I now have all the steps in place. Still needs some tweaking, but I am happy I am now going the right direction. Even more happy as I was worried this would falter the whole project. The examples there show a really simplified listview process that helped to follow the steps of the complex one that the genie builds.

      I think I am the verge of getting this whole project squared away now as there is an addin to the demo program that also manages the inventory issue and receipting in a field environment. It does some great things all based on scanning barcodes and lots of listviews that items can be easily removed if issued incorrectly at POS without the need to touch the tables. What I have discovered here now makes me happy that I can duplicate that as well.

      When I get this finished to a user stage for the first segment, I will be happy to share results if interested. I am about a month away from getting to this stage though.

      I would like to Alpha provide more info the Listview structure. They have added a powerful control but only give basic instructions on it.
      -----------------------------------------------
      Regards
      Mark Pearson
      [email protected]
      Youtube channel
      Website

      Comment


        #4
        Re: Some ideas please

        Here is a demo of what I ended up doing with this problem (No awful sound this time) http://www.onestopsolutions.biz/demo2/ Suffice to say the steps show.

        1. Selection of equipment
        2. Commencement of work order - at this point nothing was saved until user clicks next.
        3. Workorder created - as there were three serial numbers selected, one workorder was created for each one.
        4. Additional stuff added. Parts used were added. When next is clicked the the three work orders are updated, Parts are added to the parts used on each work order. Time for repair is added to the event log of each work order. If a part was not in stock that part is added to the order now list based on the qty and number of WOs. If part in stock, stock level is reduced. IF min levels of stock reached it is also added to the parts order list.

        If after step 2 nothing else is done, the user need only go to the open work order to update. key difference is that they will only be working on the work order of the one item they will be now looking at, not the original three.
        -----------------------------------------------
        Regards
        Mark Pearson
        [email protected]
        Youtube channel
        Website

        Comment

        Working...
        X