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
Devcon 2020 Goes Virtual! LEARN MORE >

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

Can someone tell me what the violated.dbf is please...

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    Can someone tell me what the violated.dbf is please...

    Whilst running a post script (converted operation) in V11, I got the attached message. I do have a v10.5 application running alongside my V11 development system but there is no crossover of data tables. I clicked OK and then ran the script again with no problems. Just a bit confused as I have never seen this before...
    Attached Files
    Tags: None
    #2
    Re: Can someone tell me what the violated.dbf is please...

    Do full text search of the inline documentation for violated.

    Violated Expression Table
    A table created by certain Operations if the field rules of the master or transaction table will be violated by the Operation.
    Alpha keeps the violated.dbf in the user temp directory so it is common to any open instance of Alpha. The explanation probably should say

    might be violated
    There can be only one.

    Comment

      #3
      Re: Can someone tell me what the violated.dbf is please...

      Tried that, still no wiser. The only reference I could find related to post operations and violated was to do with updates to the transaction table and field rule conflict...

      Originally posted by Stan Mathews View Post
      Do full text search of the inline documentation for violated.



      Alpha keeps the violated.dbf in the user temp directory so it is common to any open instance of Alpha. The explanation probably should say

      might be violated

      Comment

        #4
        Re: Can someone tell me what the violated.dbf is please...

        The only reference I could find related to post operations and violated was to do with updates to the transaction table and field rule conflict...
        Exactly. When running an operation Alpha keeps track of problems with executing the operation due to field rule conflicts with what the operation does. It stores that information in the violated.dbf. If no problems occur then the violated.dbf is closed and used later during the next operation.
        There can be only one.

        Comment

          #5
          Re: Can someone tell me what the violated.dbf is please...

          I understand that, but there are no records in the violated table and no field rule issues that I can see, also the second time I ran it no error message appearead (maybe it clears down the table when an operation runs successfully), so I suppose I am asking what could cause this to happen other than the limited explanation provided in the wiki.

          Comment

            #6
            Re: Can someone tell me what the violated.dbf is please...

            what could cause this to happen
            Two operations were running at the same time on the same machine under the same version of Alpha. Doesn't matter that they are in different databases, doesn't matter if the tables are different, doesn't matter if no violations were found, not even sure if it matters that there actually are any field rules in the tables against which the two operations were runnning.

            You start an operation running. Alpha grabs the attention, exclusively, of the violated.dbf and says "no matter what else happens, you stay ready to make notes if this operation has a problem."

            You start another operation going, Alpha trys to get the attention of violated.dbf ...........whoops, conflict.

            You try to start the other operation again, first operation is now done, no problem.
            There can be only one.

            Comment

              #7
              Re: Can someone tell me what the violated.dbf is please...

              OK, now I get it.
              So the relevant Alpha process should really differentiate between ADBs but doesn't, therefore it's a glitch in the tool.
              BTW they are different Alpha versions V10.5 and V11

              Thanks for clearing it up, however, I am concerned now that unrelated operations may fall over because two instances of Alpha are running at the same time and simultaneous operations commence.

              Hmmm...

              Comment

                #8
                Re: Can someone tell me what the violated.dbf is please...

                The usual advice is to convert the operations to code, incorporate that code in a udf that returns a logical result, call the udf and check the result. The call to the udf tests the logical result and tries to reprocess it after a delay (fixed number of tries before displaying a warning).
                There can be only one.

                Comment

                  #9
                  Re: Can someone tell me what the violated.dbf is please...

                  Actually, I apologise to Alpha they do have it covered.
                  In the V10.5 ADB I just found the private path directory in settings and have changed the folder to a new one 'ALPHATEMP' that I created in the TEMP folder itself.
                  Ran an operation and the violated.dbf now resides in this folder.
                  So, shouldn't have this issue again.

                  Thanks

                  Comment

                  Previous template Next
                  Working...
                  X