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

Ref. previous topic bug report

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

    Ref. previous topic bug report

    I am really at my wits end with the problems referred to in my previous topic "bug report". I sent a bug report twice to Alpha about this problem and have not even had an acknowledgment from them. If you read the topic you will see that other people are having similar problems as me.

    The application is based on the Alphasports template and the problems are in the invoice form which is based on the set in alphasports with �Invoice_header� and an embedded browse �Invoice_items�. The autoincrement for new record is based on Dr Peter Wayne�s autoincrement script. Because when I used the autoincrement in field rules if two operaters were entering new records the invoice items from the other operator would appear on their screen.

    One of the suggestions from the bug report topic was that when You go to new record you save the invoice header with the new invoice number and go into change mode to complete the invoice, I have implemented that but it still has not solved the problems.

    The problems are the following:-

    1) If you need to find an invoice to make a change or addition to the invoice items you then cannot navigate backwards or forward using the navigation buttons , you have to close the form and reopen to navigate.
    2) When you need to add new items to an existing invoice when you save that item the invoice header jumps to the next invoice so you end up adding the items to the wrong invoice.
    3) Also I have a save button on the bottom of the form if you click on thet after making changes it jumps to the next invoice. That button also has a script to save the invoice suptotal and total calculated fields into a normal field.

    All these problems do not happen if you use the system as a single user only on the network with more than one operator working.

    If anyone knows a different way to solve this problem I would appreciate an answer.

    Kind regards
    David

    #2
    RE: Ref. previous topic bug report

    Your implementation could be checked by another set of eyes.

    You could determine if your app fails on all networked systems, or just a particular client's. And, if it's at only one client's is it one machine or all?

    What operating system are they using?
    If it's Win98 are they regularly rebooting?
    If it's Win2000 or later has opportunistic locking been disabled on all machines?
    How much memory do they have?
    Are they multi-tasking other large Windows applications at the same time they're doing data entry in A5?
    Is their network in good shape?
    Are Windows resources being stolen by hidden bots?
    Is their Antivirus utility scanning all changes to the database folder before committing them to disk?

    -- tom

    Comment


      #3
      RE: Ref. previous topic bug report

      David

      Since the process you describe is a common method, and the problem is not, there may be other issues at work. Tom makes some very good suggestions, but one comment caught my eye

      "you have to close the form and reopen to navigate."

      This is an issue I have encountered since A5V4, and was able to track to corrupted indexes. This could occur in either the parent table or child, or both. The reasons for the corruption were traced to a number of sources. Indexes with a filter, and the filter expression not being able to evaluate, referential integrity turned on and locking the child table when the parent was in change mode, adding / editing child records with xbasic. Closing and reopening the form allows the indexes to unlock and build correctly.

      If you are doing any of the above, there are limited solutions. Verify the filters will always evaluate or remove them, remove referential integrity, limit modifying child records with xbasic. In one application where I must use a filtered index in the child table, and also add / edit /delete child records in xbasic, I close the form in the code and then reopen after the code completes, with an added pause in the process to allow the indexes to build correctly.

      Since the issue seems to occur only in a networks app, index corruption seems to be the likely culprit. Also search the A5V5 forum for "opportunistic" to get some info on opportunistic file locking.

      Jerry

      Comment

      Working...
      X