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

Write conflict on active link SQL table

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

  • Write conflict on active link SQL table

    I'm just starting the process of migrating a Filemaker solution to A5 and have run into a wall. I have an active link table connected to a sql express 2005 source and when I try to change a record in it on a desktop form, I almost always get a Write conflict warning saying the record has been edited by another user. I say "almost" because once or twice, and only on certain records, it will save the changes. Stranger still, on a web grid connected to the same table, records update on it no problem. FYI, there is no one else connected to the data. Any suggestions?

  • #2
    Re: Write conflict on active link SQL table

    Originally posted by JohnD88 View Post
    I'm just starting the process of migrating a Filemaker solution to A5 and have run into a wall. I have an active link table connected to a sql express 2005 source and when I try to change a record in it on a desktop form, I almost always get a Write conflict warning saying the record has been edited by another user. I say "almost" because once or twice, and only on certain records, it will save the changes. Stranger still, on a web grid connected to the same table, records update on it no problem. FYI, there is no one else connected to the data. Any suggestions?
    i am not seeing this problem in my tests in which i have a copy of northwind in sql server.

    we can give you a quick answer to your question if you send us the table structure of your sql server table.

    you need to go into the sql server express management studio and right click on the table. you should see a command to copy the sql create table statement. that's what we need.

    once we have the create table statement we can recreate an identical table and test the update.

    in the mean time, i suspect that you can work around the problem by editing the active link definition and changing the 'update sql' statement from auto generated to custom.

    then when you create your custom update statement, just select the primary key field, not all fields, for the WHERE clause in your Update statement.

    thanks

    Comment


    • #3
      Re: Write conflict on active link SQL table

      Mr. Rabins,

      Thank you for your quick answer. I think I finally found the sequel create statement from SSMSE which is attached. I did change the UPDATE statement on the active link to Primary Key only and it worked. Now I can edit the records. I received a warning when I did this. Does this interfere with the Optimistic record locking? Thanks again for your quick reply.

      Comment


      • #4
        Re: Write conflict on active link SQL table

        Originally posted by JohnD88 View Post
        Mr. Rabins,

        Thank you for your quick answer. I think I finally found the sequel create statement from SSMSE which is attached. I did change the UPDATE statement on the active link to Primary Key only and it worked. Now I can edit the records. I received a warning when I did this. Does this interfere with the Optimistic record locking? Thanks again for your quick reply.

        thanks for the sql create statement.

        i was able to create a table and populate it with dummy data and then create an active-link table.

        i did not have any trouble at all doing updates.

        i did not need to change my update where clause to be 'primary key only'. it is possible that this is because I am using a pre-release of the next update which will come out next week some time.

        in any event, when you set the update where clause to be 'primary key only' a5 was just warning you that it would NOT be able to trap 'optimistic lock errors'. it is just a warning that is displayed to make sure you know what the consequences are of modifying the system generated update where clause.

        Comment

        Working...
        X