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

posting an assembly

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

    posting an assembly

    I am trying to think up a way to let our person doing inventory post any number of kits of a certain part number. Right now a kit contains various amounts of 19-20 items. I could make a database defining the kits. But how can I make it post all those line items against our inventory? Any suggestions?

    Jason
    [email protected]

    #2
    RE: posting an assembly

    Jason:

    I had a similar situation I solved with a script that actually went to the items database and entered these receipts.

    If the kits always contain the same 19-20 items - Yes - make a database with all those items in a slngle record for each kit. The script would then set variables to each of the items; open each line-listed part in that other database and add the number received. If you're in A4V6 you can easily open the records using 'find'; then use field_enter script command to increase the count for that single item. The script that I did ran unbelievably fast taking little more time than it took to display the activity dialog.

    If you'd like more help, it's [email protected]

    Ken

    Comment


      #3
      RE: posting an assembly

      I tried something similiar to this a couple of years ago. I was using a SET.

      Parent was PRODUCTION, child was PARTSBOM.

      Entering the work order number in the production table returned the part id from the ORDER file. The part id would relate to all records in PARTSBOM matching part id. All component parts and finished assemblies had one record in PARTSBOM. The parent PRODUCTION was set to add-post to the field in PARTSBOM "stckqty" (stock-quantity) and the related components listed from PARTSBOM were set to subtract-post also to PARTSBOM for the parts that were used to make the completed assembly.

      However, the only posting that occured was the parent PRODUCTION record, that would get add-post to the correct record in PARTSBOM, and the "first" and only the first related record in PARTSBOM would get subtract-posted. I fiddled with it, but could never get all the related parts in PARTSBOM to work correctly.

      I'm sure some work with scripting could get the desired results, but at the time I was not familiar with scripting to do that. Maybe not even now.

      But anyway, that's how I tried to tackle the issue.

      Kindest regards,
      Mike

      PS: I did find that if I tabbed to the related PARTSBOM region in the Production Record entering screen, highlighted each related record and put each child record in "change" mode and then saved by pressing F10, the post would work for all related records. I didn't think the time required to do that to post anywhere from 2 to 25 components used would be worth the effort unless done automatically.
      Thank you,
      Mike Konoff

      Comment

      Working...
      X