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

Bad Records

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

    Bad Records

    Hi All,

    I have attached a database with a bad record mystery.

    Would appreciate more shared opinions on the problem so that it can be avoided in the future.

    Michael

    #2
    RE: Bad Records

    Michael:

    Following your 'text letter' instructions, I cannot get either of your forms to fail. I don't get the machine lockup, program lockup or any other of the things you describe.

    Am I doing something wrong? Geez - it looks nice!

    Ken

    Comment


      #3
      RE: Bad Records

      Michael,

      As well for me, no problems with the forms/browses. I did notice on formA there is an action script for the oninit event which attempts to set "by_date" to "date().

      I can't find any variable, control, etc with the name "by_date".

      I can't imagine that this would cause your problem but seems strange.

      Stan
      There can be only one.

      Comment


        #4
        RE: Bad Records

        Stan and Ken,

        Thanks for sharing my puzzle.

        I have attached a new zip containing the original 'Monitor.dbf' and a duplicate 'Reserve.dbf'.

        Can you please destroy the original database and try again using this attachment.

        Thanks

        Michael

        Comment


          #5
          RE: Bad Records

          Stan and Ken,

          Thanks for sharing my puzzle.

          I have attached a new zip containing the original 'Monitor.dbf' and a duplicate 'Reserve.dbf'.

          Can you please destroy the original database and try again using this attachment 'Badrecords2.zip'.

          Thanks

          Michael

          Comment


            #6
            RE: Bad Records

            Michael,

            I don't have a thoroughly complete answer, but here are some clues.

            I noticed that FormA and FormB differ in one important respect. Although they're based on the same set of tables, FormB does not specify an ordering expression for the child table, Monitor. FormA, on the other hand, specifies: invert(WHEN) as the display order for the linked child table records from the same table (Monitor).

            When the ordering expression is removed from the properties of the linked child table in FormA the crashes stop. Limited testing indicates that FormA will then behave like FormB.

            In other contexts it's been my experience that you cannot change the display sequence of a linked child table in a form that's based on the set. The 'ordering' of the child tables is occurring at the set level and apparently may not be 'over-ridden' at the form level. What I've successfully done to overcome this limitation in my own work is to create different versions of the set, to specify a different linking sequence which has the effect of displaying the child table records in the proper sequence. This is done specifying an expression as the link field in the child table of the set design. The expression would contain a concatenated string of fieldnames, the first of which matches the link field specified for the primary table, and the second of which would be the field you want the child table to be ordered by, and it would be specified as 'inverted'.

            In your case I've tried a similar approach and have had difficulty building an expression which concatenates the MON_ID field (numeric) with the inverted version of the WHEN field (date). Given the limited time that's available I've about decided one cannot mix these in a single expression.

            I suggest you simply build an inverted set and base your form on it instead. You will be able to easily adjust the display order of the primary table records, and can display them in a browse if you wish.

            -- tom

            Comment


              #7
              RE: Bad Records

              Tom,

              Thanks for your interest.

              My example is part of a large Health & Safety application that I developed and has been in use several years.

              Both Forms A and B are based on the same set and both have a form property sort order set to the 'Why' field in the parent. The lockups do not stop in my example even if the sort order is removed.

              (In my sample Form A has a couple odd sessional variables that are not in use for my sample. These should not have been included in zip sample and can be discarded)

              I am sure that the problem is with the two bad records that I have identified in Monitor.dbf. If these records are deleted and the table packed OR the 'When' field dates for those two records (Oct 17th 2003 and Oct 25th 2002)are edited|changed to say 2003 instead of 2002 then all is OK.

              Michael

              Comment


                #8
                RE: Bad Records

                Michael,

                Perhaps your 'real' database is different, but the one you posted here uses an ordering expression in FormA that's missing in FormB.

                Open FormA in design mode.
                Click Form on menu bar
                Select Properties
                Select Filter/Order properties.

                You will find a representation of the set, showing both the Mon_type table (primary) and the Monitor table (child).

                The ordering expression for the primary table is the same on both forms.

                HOWEVER, check the ordering expression for the child table, Monitor. I think you'll find a difference, and that the problem you're having goes away if you remove the ordering expression for the Monitor table in FormA, as originally recommended.

                -- tom

                Comment


                  #9
                  RE: Bad Records

                  Tom,

                  Yep, thanks I had set that sort years ago and forgotten it was there. Strange though this application is being used extensively and has only just thrown up this bug. Also strange why changing the date on one record should also eliminate the lockup. The record in question is highest date in 'Why' category 'Exposure to blood'.

                  I think a sort on a child record when displayed in a set will always give uncertain results.

                  Michael

                  Comment

                  Working...
                  X