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

Beware builds past 2736-3523

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

    Beware builds past 2736-3523

    I've been struggling for two days with some very bad behaviour in an embedded browse. Because I'm doing a lot of development right now I though it was me... but still I couldn't understand why I was running into problems because I'd tested the basic functionality of this particular form over a month ago and it was fine. I have been making some changes, but not to the basic underlying logic of the code.

    Since the beginning of March I've been putting in the Alpha updates... and still making changes...

    I have a form with an embedded browse with transaction records on it. I enter credit card type, # etc and the all the transaction records get updated based on just one row of the browse. It all worked.

    With recent builds the updates to the records work, but any movement off the current record changes the contents of the last record to the contents of the first record.

    I thought it was me... it's not... it's the builds past 2736-3523

    #2
    Re: Beware builds past 2736-3523

    Hi David,

    Have tried 2787_3538?
    Regards
    Keith Hubert
    Alpha Guild Member
    London.
    KHDB Management Systems
    Skype = keith.hubert


    For your day-to-day Needs, you Need an Alpha Database!

    Comment


      #3
      Re: Beware builds past 2736-3523

      Your right, recent builds have had odd behaviors. I've already given up and reverted to earlier builds. I noted that fields become empty on a record when it is saved, leaving the record partially filled or empty. The record cannot be edited then and has to be deleted from the tables and sets part of control panel.

      Comment


        #4
        Re: Beware builds past 2736-3523

        Yes... the only build that was stable for what I'm doing is the one I posted about. Tried the latest one and it's bad as well.

        Comment


          #5
          Re: Beware builds past 2736-3523

          Yes.
          I am having similar issues. Every new build seems like it comes with new issues and something that worked perfectly before no longer works... this has been very frustrating!!!! for myself and my clients!
          Lee Goldberg
          Software Development and Sales
          Shore Consultants Ltd.
          [email protected]
          www.shorecon.com

          Comment


            #6
            Re: Beware builds past 2736-3523

            Luckily... if you can call it that... I'm the client in this case. Although I've wasted a couple of days and a lot of frustration I've re-learned a valueable lesson. However, I am charging people's credit cards so it could have been really bad. Since the app is new I'm watching and double-checking all calcs and function.

            It's tough to put in a new software release and test all functionality in an app. I usually go through the major stuff.

            This bug actually hurt... it changed data... and if you weren't really sharp about what you're seeing you'd miss it... a bit dangerous.

            Comment


              #7
              Re: Beware builds past 2736-3523

              David, I haven't seen this behavior here. Please post an example with step by step instructions for us to follow. And, have you submitted a formal bug report? Thanks. -- tom

              Comment


                #8
                Re: Beware builds past 2736-3523

                I'll try to get something posted today. When I have something together I can submit a bug report. But I have confirmed that every release since 2736_3523 is bad.

                Comment


                  #9
                  Re: Beware builds past 2736-3523

                  David, your work will help Alpha identify the issue, since you've pinpointed the time when the problem manifested itself. However, they'll still need to be able to replicate the bug to fix it.

                  Comment


                    #10
                    Re: Beware builds past 2736-3523

                    David, do you see this only when there are more linked child table records than the browse can display in its alloted space? -- tom

                    Comment


                      #11
                      Re: Beware builds past 2736-3523

                      Hey Tom,

                      I have a main form where I enter a membership record.
                      That membership can be paid for in one payment or multiple payments.
                      If a choice is made for multiple payments then 1 record is written to a transactions table and the transactions form is displayed filtered on the member #.

                      There is a dropdown box on the transaction form allowing you to choose the number of payments you want to create.

                      One transaction record is currently displayed.

                      Even though only 1 record is displayed the browse has viewing room for about 15 records.

                      You choose 12 payments and I look at the full amount, divided it by 12 and write 12 records to the transaction table and delete that one original record.

                      The form is then refreshed and the 12 records are displayed. My cursor is now on the 1st record in the embeded browse.

                      There is information I must fill in now... the credit card number, expiry date and type of payment, e.g. Visa

                      If I click or tab out of the first record all 12 records are updated with the new information entered. I do this in code - I get the table, get the records and loop through the records updating. The code is run from the CanRowChange Event of the embeded browse.

                      The browse is now refreshed and all the records contain all the information I need.

                      Now... if I tab or click anywhere in the browse the very last record is now changed - all it's data is changed to the exact same data as the first record.

                      Even though I have code on the CanRowChange Event of the browse, the code does not change everything in the record, only specific fields. However, everything on the last record is changed because of the latest releases.

                      The record display behaviour of the embeded browse is further unstable as well. Sometimes, when tabbing or clicking out of the first record the browse will blank. Pressing a page up or down key will display the records. Pressing page up or down again will display all the records in the table... not just the filtered records.
                      Last edited by Davidk; 03-08-2010, 10:49 AM.

                      Comment


                        #12
                        Re: Beware builds past 2736-3523

                        David, your sitation is more complex than what I was seeing here.

                        Presumably your form is based on a set of tables. And, presumably the embedded browse object is showing records from a one to many child table, right? Do you have referential integrity enabled?

                        If so do the problems clear up if you disable cascade of changes and deletes?

                        Comment


                          #13
                          Re: Beware builds past 2736-3523

                          Add me to the list! I had similar problems and not only did I revert to the previous build, I had to restore a prior version of my table. I didn't submit a bug report because I don't have time to make a "dummy" database to send.
                          What I had a major problem with is with embedded browses. Child records would be overwritten by other child records. Also, adding new records via a pop-up form did not honor field rules. Finally sort order was being ignored. I have not tried the March 4th build yet ... waiting for reports that its stable.

                          John Walsh

                          Comment


                            #14
                            Re: Beware builds past 2736-3523

                            If we can't reproduce the problem ourselves, we can't fix it. I have seen Tom's bug report (thanks, Tom!), and the response 6 hours later that his problem has been fixed, but that doesn't mean that Tom's problem and yours are identical.

                            Comment


                              #15
                              Re: Beware builds past 2736-3523

                              It doesn't mean it identical, however, when an application is functioning properly and then the next build is installed and problems start popping up that were not problems before. The easy solution is to restore to the previous build.

                              Most of us are independent consultants/business owners who don't have time to be hassled with these issues. When six hours is spent fixing something, that is six hours I can't bill my client for and it is 6 hours of billable time lost. The simple logic is that something works, a build is installed and nothing else changes and something no longer works and it is frustrating.

                              I have documented my problem in this post http://msgboard.alphasoftware.com/al...ad.php?t=85345

                              The suggestion for a solution that was provided did not work. But the point is it worked before and nothing changed but the build.

                              Reverting to a previous build is the easiest, most cost effective solution.
                              Lee Goldberg
                              Software Development and Sales
                              Shore Consultants Ltd.
                              [email protected]
                              www.shorecon.com

                              Comment

                              Working...
                              X