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

Embedded browse & disappearing records

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

    #61
    Re: Embedded browse & disappearing records

    Any results on this? I have a customer experiencing the same symptoms.
    • I created the browse from the browse object, not a saved browse.
    • Browse works fine for a while, then when records are being edited, seemingly at random, data appears to vanish from some fields in the browse.
    • Data appears duplicated from say, record 9 to record 10. So user thinks they have entered something twice in error. So they edit the apparently duped record, only to discover the records were right all along, but the browse was displaying data erratically.
    • Using the duplicate record function produces inconsistent results with the browse.
    • The browse has about 15 columns, one is a calculated field.
    • I tried the patch listed above, but it didnt fix the problem...
    • My user is accustomed to being able to use the keystrokes to duplicated browse records, as this function worked very well in their version 4 Dos database.... but it is not working consistently here..
    Please help!!!!

    Thanks!!!

    Rich Kerr
    Rich Kerr
    http://www.richkerr.com
    [email protected]

    Comment


      #62
      Re: Embedded browse & disappearing records

      Another problem that seems to consistently happen is when you scroll to the bottom of a list in an embedded browse the last record is displayed several times.
      Bob Whitaker

      Comment


        #63
        Re: Embedded browse & disappearing records

        Originally posted by Bob Whitaker View Post
        Another problem that seems to consistently happen is when you scroll to the bottom of a list in an embedded browse the last record is displayed several times.
        Now if we could only get it to do it on demand so we could do a bug report.

        Comment


          #64
          Re: Embedded browse & disappearing records

          Doesn't this mostly happen when a browse screen is larger than the number of records ...mentioned here I think and many other threads. Also it has happened (or similar) when the last record showing is not quite all the way in the browse screen and by either reducing or increasing the browse screen size it eliminated certain problems.

          I noticed a few things are not as "bad" as prior versions with version 8 but most of the known issues with browses remain.
          Mike
          __________________________________________
          It is only when we forget all our learning that we begin to know.
          It's not what you look at that matters, it's what you see.
          Henry David Thoreau
          __________________________________________



          Comment


            #65
            Re: Embedded browse & disappearing records

            Originally posted by MikeC View Post
            Doesn't this mostly happen when a browse screen is larger than the number of records
            Yes. When this happens again I wll check my window size. You now have me wondering if this happens when I expand the window size bigger then the default size.

            Comment


              #66
              Re: Embedded browse & disappearing records

              Originally posted by MikeC View Post
              Doesn't this mostly happen when a browse screen is larger than the number of records ...mentioned here I think and many other threads. Also it has happened (or similar) when the last record showing is not quite all the way in the browse screen and by either reducing or increasing the browse screen size it eliminated certain problems.

              I noticed a few things are not as "bad" as prior versions with version 8 but most of the known issues with browses remain.
              I vigorously disagree with this.

              What are these 'known' issues? They certainly are not know to us at Alpha.

              Any issue that is reported to Alpha (with a sample database that allows us to reproduce the problem) is promptly addressed. A bug report that does NOT contain sample data or instructions on how to reproduce the problem is worthless to us.

              There are no outstanding bug reports related to browse that are open at the moment.

              Comment


                #67
                Re: Embedded browse & disappearing records

                Originally posted by richkerr View Post
                Any results on this? I have a customer experiencing the same symptoms.
                • I created the browse from the browse object, not a saved browse.
                • Browse works fine for a while, then when records are being edited, seemingly at random, data appears to vanish from some fields in the browse.
                • Data appears duplicated from say, record 9 to record 10. So user thinks they have entered something twice in error. So they edit the apparently duped record, only to discover the records were right all along, but the browse was displaying data erratically.
                • Using the duplicate record function produces inconsistent results with the browse.
                • The browse has about 15 columns, one is a calculated field.
                • I tried the patch listed above, but it didnt fix the problem...
                • My user is accustomed to being able to use the keystrokes to duplicated browse records, as this function worked very well in their version 4 Dos database.... but it is not working consistently here..
                Please help!!!!

                Thanks!!!

                Rich Kerr
                You need to supply a sample database that allows us to reproduce the problem. Without that, it is impossible to comment.

                Comment


                  #68
                  Re: Embedded browse & disappearing records

                  Selwyn,

                  :) I have read every message posted for the past year and a half....and of course many others in my quests for answers. The main "issue" I find as a common theme to browse problems are the refresh issues, some of which can be resolved with a lot of trial and error (due to no one fix)....but other times the only way to refresh the browse is to close and then reopen the form in which the browse is on.

                  Another common problem are the "disappearing" and multiple "copies" of records. Of course the records are not actually disappearing but are not visible and the copies are not true records but like ghosts of a single record.

                  The third most common browse problem is the scrolling issue where the scroll bar does not match the screen.


                  EDIT: This is just but one thread that discusses the browse.
                  http://msgboard.alphasoftware.com/al...Browse+problem

                  LATER:
                  http://msgboard.alphasoftware.com/al...Browse+problem
                  Last edited by MikeC; 02-01-2008, 11:47 AM. Reason: Link added
                  Mike
                  __________________________________________
                  It is only when we forget all our learning that we begin to know.
                  It's not what you look at that matters, it's what you see.
                  Henry David Thoreau
                  __________________________________________



                  Comment


                    #69
                    Re: Embedded browse & disappearing records

                    Originally posted by Selwyn Rabins View Post
                    I vigorously disagree with this.

                    What are these 'known' issues? They certainly are not know to us at Alpha.

                    Any issue that is reported to Alpha (with a sample database that allows us to reproduce the problem) is promptly addressed. A bug report that does NOT contain sample data or instructions on how to reproduce the problem is worthless to us.

                    There are no outstanding bug reports related to browse that are open at the moment.
                    Take a deep breath.

                    I am going to go out on a limb and say that we as users & developers see these problems. We can not put our finger on how to RECREATE the problem. There lies the problem. You can not fix a problem until we show you the problem exists. This board is good so we can talk and read about what others think the formula is to get the problem to occur.
                    I may not witness these problems for a few day and then it might show up. As of right now I do not know if I close the form and reopen is the only way to fix when it starts happening. I do not know if I am in edit, new or view mode. If I could give you an example and make it happen every time, you would have a bug report from me, but since I can not make it happen we wait.

                    Maybe what we need is a take a screen shot everytime this happens and post. Then maybe someone can view and get some ideas how to recreate.

                    How about a button that goes to a script. When we see this happen we press the button. A script runs and makes a log of everthing that is going on at that moment. I had a script when I used Paradox that when an error happened it made a log file of everything. I could then pull the log up to see what every variable that was in memory was and value, open forms, records viewed, date, time, user, and such.

                    Comment


                      #70
                      Re: Embedded browse & disappearing records

                      FWIW, the ghost records and disappearing data are driving me nutz. database compact will not stop it. Next time it happens, I'll see what I can document.

                      kenn
                      TYVM :) kenn

                      Knowing what you can achieve will not become reality until you imagine and explore.

                      Comment


                        #71
                        Re: Embedded browse & disappearing records

                        hello:

                        i changed the size of my browse to be smaller than the number of records displayed and the problem went away. changing it back to be larger than the number of records displayed causes the disappearing data. if you want i'll submit the files as this is easily recreated.


                        best regards,


                        ed

                        Comment


                          #72
                          Re: Embedded browse & disappearing records

                          Originally posted by eeetee View Post
                          hello:
                          if you want i'll submit the files as this is easily recreated.

                          Submit it to Alpha as a bug report. Then we will all benefit.
                          Peter
                          AlphaBase Solutions, LLC

                          [email protected]
                          https://www.alphabasesolutions.com


                          Comment


                            #73
                            Re: Embedded browse & disappearing records

                            hi peter:

                            please advise how to send a bug report. i've been away from alpha for some time and just can't remember.


                            best regards,

                            ed

                            Comment


                              #74
                              Re: Embedded browse & disappearing records

                              Originally posted by eeetee View Post
                              hello:

                              i changed the size of my browse to be smaller than the number of records displayed and the problem went away. changing it back to be larger than the number of records displayed causes the disappearing data. if you want i'll submit the files as this is easily recreated.

                              best regards,
                              ed
                              Please do a bug report. You do not know how may people will thank you. When I have it crop up again I will see if sizing it make problem go away. I have where most all of my browses can be resized bigger or smaller. I know I alot of time I resize it bigger so I can see all of the data. Hope you have found the problem. I know Alpha will fix it if we can show them the problem.

                              Comment


                                #75
                                Re: Embedded browse & disappearing records

                                Originally posted by eeetee View Post
                                hi peter:

                                please advise how to send a bug report. i've been away from alpha for some time and just can't remember.


                                best regards,

                                ed
                                Look under the help menu for

                                Send a bug report
                                Last edited by Stan Mathews; 02-06-2008, 03:59 PM.
                                There can be only one.

                                Comment

                                Working...
                                X