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 rule and 4.5

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

    Posting rule and 4.5

    Has any one had any problems with the built in posting rule using V4.5?

    I have a situation now where the posting rule seems to not be calculating correctly. Some times the rule will not add in the correct amount.

    For example: One of the date entry clerks keyed in an amount of 660 and only 360 was added to the inventory. I do run an audit of all entries and she did indeed key in the correct amount.

    Would it be advisable to use a custom posting rule or perhaps a posting operation?

    I do like the instant inventory update provided by the posting rule.

    One other question: What setting should be used over the network for network refresh. Is there a need to indicated anything over 0 sec? Also what about the index locking function, should this be activated as well?

    I said only one other question oops.

    Thanks

    Rodney

    #2
    RE: Posting rule and 4.5

    As for the second part of your question, Ira answered recently:

    Make sure the refresh in Settings is set to 0 (off) unless there is a real need for it (seldom is). When you go into change mode it will automatically refresh. In general, never do anything on the network that can be done on the local drive. In addition to Newtwork Optimization, both the Private directory and any temporary files should be worked with on the local drive.

    It adds up faster than you realize and multiplied by the users, can quickly slow your network to a crawl.

    Regards,

    Ira J. Perlow
    Computer Systems Design & Associates
    [email protected]
    There can be only one.

    Comment


      #3
      RE: Posting rule and 4.5

      Rodney, I don't recall any message traffic on your first issue. I would recommend that you spend some time trying to replicate the error. Once you figure out how to make it happen, describe the sequence for us here.

      -- tom

      Comment


        #4
        RE: Posting rule and 4.5

        Rodney,
        I've seen multi-user distributor software costing over $100,000 come up with incorrect numbers in "on line" updated fields. If you have a multi-user system with transactions increasing and decreasing the on hand amount in your item table, there is always, in my opinion, a possibility for errors. Keep in mind that the posting rules depend on indexes. You may be fortunate enough to find some logic that caused this particular problem, but the next time you may not. I use the posting rules to update a field functioning as an "unposted inventory change" amount. This is kept throughout the day and netted into an "actual count" field to provide a "calculated current on hand" amount. At the end of the day I zero out the "unposted amount" and read through the transactions and update the "actual count" field. I then mark the transactions as posted so that they will not be a part of the next update. If the "calculated current on hand" is incorrect, hopefully it will only be incorrect for a day.
        John

        Comment

        Working...
        X