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

version 4.5 network issues

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

  • version 4.5 network issues

    Has anyone had this problem?
    I have a field rule in a table (invoice) for the invoice # to be "unique". The user is running the runtime engine and sometimes, the system allows duplicate entries on this "unique" field. The machine is 98se on a Win 2k server, not network optimized (she is the only one entering data). I cannot duplicate any records on any of my machines, or accross my network using the same setup. Any Ideas?

  • #2
    RE: version 4.5 network issues

    John, if data entry is occuring through a set based form, and the set uses referential integrity, this article may be illuminating:

    http://www.learnalpha.com/DisappearingRecords/DisappearingRecords.htm

    It discusses a non-obvious way duplicate fields can occur.

    -- tom

    Comment


    • #3
      RE: version 4.5 network issues

      Tom, Thanks for the reply. I did read the article but it's no help. I don't use referential integrity in the set and the data is entered into a table (invoice), not the set (payroll). Again, I cannot duplicate the problem in my office either on the network or working stand alone. I am guessing that the problem lives within the machine my client is using, or within the network at their site. The "unique" test field rule works "most" of the time, but each week, there are usually 10-15 invoices that were entered using duplicate invoice numbers. this is out of around 1000 records. I'll keep scratching my head. Thanks again.

      Comment


      • #4
        RE: version 4.5 network issues

        John,

        One last idea:

        Examine the duplicates closely. Maybe the display has been formatted so that they seem to be exact matches, but in reality the stored data is a bit different. For char type fields I've found it necessary to use a uniqueness expression which trims leading and trailing blanks, and forces everything to upper case letters, before the comparison is done.

        -- tom

        Comment


        • #5
          RE: version 4.5 network issues

          Excellent suggest Tom, I will put that to the test.

          Comment

          Working...
          X