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

Disappearing data - or so it seems

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

  • Disappearing data - or so it seems

    Good morning,

    In a sub-form, when the user switches from the parent form to an existing record in the sub-form (parent form fields are from the set, and sub-forms are from individual tables, all linked by SIT_ID), the sub-form's data appears to simply disappear when the tab key is pushed.

    What's left is that the first several fields' data disappears. When the user pushes the PageUp button, the data reappears.

    The really odd things is that it is only the first few fields' data that disappears. The last few fields' data remains visible.

    I'va packed, updated indexes, to no avail. I also have the most recent v7 patch installed.

    Any ideas?

    Thank you,
    Wanda

  • #2
    Nope. Sorry. If others are silent, go ahead and post a working copy of the app here with instructions for us to follow to see the behavior.

    -- tom

    Comment


    • #3
      Wanda

      I would be most interested in the solution to your problem - I have a similar problem with only 1 of my apps.

      Chris
      If It Works First Time, There's Something Wrong!!!

      Comment


      • #4
        db attached, with instructions

        1. Open Sites form.
        2. Place curser in any field of the parent form, for instance, in the Street field.
        3. Scroll down to the bottom of the form and click on the Buildings tab.
        4. Place curser in the Square Feet field and press Tab.

        It is haphazzard. You should see the data in the fields along the bottom inside a box (labeled Shut-off Locations). You should also see that the data in the fields on the left side of this tabbed sub-form (Site ID, Building, Quantity, Construction) disappear.

        If the fields don't disappear when you follow these steps, go back to step 1 and press PageDown for a different parent record and repeat the remaining setps.

        Many thanks,
        Wanda

        Comment


        • #5
          db attached

          Oops...here's the db.

          Comment


          • #6
            The remaining fields are memo fields

            I discovered that the fields that remain populated are all memo fields...so, it's as if pressing tab actually opens a new record, except for the memo fields...are there still problems with using memo fields?
            Wanda

            Comment


            • #7
              Wanda,

              I took a look, and can confirm the behavior you're seeing. Cannot diagnose this for you.

              You've placed a series of subforms on separate pages of a tabbed control, each subform is for a one to many child table that's part of the set.

              The set supporting your form includes 10 linked one to many child tables, and referential integrity is enabled for all 10 tables.

              Your set bears the same name as one of its tables.

              I have no experience doing it this way. My design bible is "Simplify Your Applications" at www.learnalpha.com.

              The field blanking you are experiencing may be caused by some process in the form, field rules, or the subform starting a new record when you are not expecting it.

              -- tom

              Comment


              • #8
                Well put, Tom. In my opinion, the app is quite simple...so, I guess that's a matter of opinion.

                I suspect it is something with the memo fields, which have been pesky over the years, and because it's only the memo fields that remain populated...

                I'll keep searching and will post any success.

                Thank you,
                Wanda

                Comment


                • #9
                  Wanda,

                  The app may be simple, I wouldn't argue that. But the form you've built for data entry is complex.

                  Here's a link to the article I referenced. I recommend it to you.

                  http://www.learnalpha.com/SimplifyYo...ifyYourApp.htm

                  The correct article title is "Simplify Your Applications for Better Performance"

                  -- tom

                  Comment


                  • #10
                    It's necessary to place all parent and child data on one form

                    Thank you, Tom. I'll take a look. I wouldn't normally put all the tables on one form, however, due to the nature of what this database will be used for, it is necessary that all data related to each parent record be simultaneously visible for the sake of speedily searching through the records to find the right shelter to open.

                    This database contains information on the county's Mass Care Shelter sites that can be opened for displaced individuals due to a disaster such as a residential complex fire, an earthquake, a flood, etc.

                    This database wouldn't serve that purpose very well if the operator has to view several different forms in order to determine which one shelter site has all the necessary "services" such as feeding, cooking, sleeping, sanitation, payphones, and is suitable for such needs as a storm shelter, or earthquake bracing, or not used by fire departments, etc.

                    Wanda

                    Comment


                    • #11
                      Hey Tom,
                      I looked at the article you recommended. Thank you. It doesn't apply to my situation or to my needs, however, because my database is not networked; nor could I design it to where a user could search for any one thing when trying to find a proper shelter. Each disaster brings its own unique qualities, so all of its amenities need to be ascertained at a quick glance.

                      I do have a two menus for specific searches, however they both return the data via the Sites form.

                      Can you see any place where I can change the design and still be able to provide all the data at a glance?

                      Thanks,
                      W

                      Comment


                      • #12
                        Hi Wanda,

                        I looked at your app. I haven't really found out the reason or cause. However, I see that your main menu is based on the Sites table. You can open the main menu and scroll through the record count from the main menu.

                        That along with a table named the same as the set makes me wonder. I would really make the main menu based off of a "Dummy" table, and I would rename the set something different from any table name.

                        I think after you do this, the problem may be easier to find.
                        Dan

                        Dan Blank builds Databases
                        Skype: danblank

                        Comment


                        • #13
                          Wanda,

                          If it were me, I'd disable referential integrity on all linked child tables. Then I'd use the complex form only for navigation and "viewing". Edits would be made using simpler forms, called from the complex form.

                          I'd change the name of the sites set, so that it does not duplicate the name of it's primary table.

                          I'd use Dr. Wayne's article called "Memos and Browses That Work" to design the data entry routines and forms for all memo field text.

                          I'd abandon the use of the tabbed object, replacing it with a Conditional Object, instead.

                          -- tom

                          Comment


                          • #14
                            Wanda

                            Does the new patch make a difference?

                            Chris
                            If It Works First Time, There's Something Wrong!!!

                            Comment


                            • #15
                              Now, you're scaring me. I don't have the time to do a total re-design, unfortunately. And the last I knew, renaming a table can create all kinda of havoc, so I'm hesitant to do that. Is this still the case? If not, then I'll rename the set.

                              Dan, I should have known to create a dummy table to base the Main Menu on. You're right. It's been a long time since I've had to design something for someone else to use - thus the necessity for a Main Menu. I'll play with renaming it, or copying it to a dummy table.

                              If renaming doesn't solve the problem, then I can consider having the form as it is now for viewing/searching, only; and hopefully be able to copy/past different sections into their own form for data entry. I'm frustrated that this should even be necessary, though...will post my results.

                              Thank you,
                              Wanda

                              Comment

                              Working...
                              X