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

1 field disappeared from report. Still saves as part of record but...

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

    1 field disappeared from report. Still saves as part of record but...

    no longer printing on report. Worked fine for awhile then suddenly stopped working. No changes made to app (user has runtime) and doesn't happen on my end.
    Rebuilding indexes, packing database, closing & re-opening app, and re-booting system hasn't helped.
    Any ideas or suggestions appreciated.
    Thanks,
    Bill

    #2
    Bill, don't overlook the possibility that the user has inadvertantly deleted the contents of the field that is not showing up on the report. Your testing should be done with the user's data. -- tom

    Comment


      #3
      Originally posted by Bill
      no longer printing on report. Worked fine for awhile then suddenly stopped working. No changes made to app (user has runtime) and doesn't happen on my end.
      Rebuilding indexes, packing database, closing & re-opening app, and re-booting system hasn't helped.
      Any ideas or suggestions appreciated.
      Thanks,
      Bill
      Originally posted by Bill
      1 field disappeared from report. Still saves as part of record but...
      - this means the field still exists in the table

      no longer printing on report.
      - if nothing prints in the area where the field value should appear this means the report definition doesn't contain a reference to the field. If the field name appears there, the report definition can't find the field.

      You should be able to send the user the support files for the table on which the report is based and solve the problem. Check here for table data dictionary file extensions.
      There can be only one.

      Comment


        #4
        Originally posted by Tom Cone Jr
        Bill, don't overlook the possibility that the user has inadvertantly deleted the contents of the field that is not showing up on the report. Your testing should be done with the user's data. -- tom
        Ah, the most logical conclusion based on the fact that the user only has the runtime. Now why didin't I think of that.
        There can be only one.

        Comment


          #5
          Stan, are you messing with me or Tom?

          Tom, I did check that and thought that was adequately addressed in the title line, but the data has saved properly as part of the records we checked.

          Maybe I'm not phrasing the question properly. I don't understand why it would print as expected, for dozens of records, and then stop printing data just from that field when nothing had changed in the application.

          Re-installing the app or the the support files in question might fix the problem but I'm more concerned with finding out what the problem is, just in case it (or some variation of it) ever happens again.

          Thanks again

          Comment


            #6
            Originally posted by Bill
            I don't understand why it would print as expected, for dozens of records, and then stop printing data just from that field when nothing had changed in the application.
            - I didn't understand that it was working for some records and not others. I thought you meant it used to work but now the field didn't print on the report at all.

            Is the report based on a single table or a one to many set? If a set, is the problem field in the one to many child?
            There can be only one.

            Comment


              #7
              Bill,

              I saw the title and was still unsure whether you're on site and have tested the report on the same network as the user and it works ok for you but not for him... OR... you're at a remote location using your own data. In fact, I'm still not sure you've tested the report using the same data as the user.

              It seems to me that the most likely causes are:

              a) report layout specs are fine and the empty spaces in the report are caused by missing data; or

              b) the report layout has become corrupt; or

              c) the report layout uses a specific index that's become corrupt.

              If you can run the report with a copy of the user's actual data, then (b) and (c) could be fixed by reindexing and / or reinstalling, assuming the user's workstation and network is in good shape.

              That's how I see it, anyway. Perhaps other ideas would come to mind if you described the set that the report is based upon, and gave us some information on the troubled field. For example when you say the field disappeared, does that mean that nothing appears, or do you get a little square box... instead of actual data?

              Hope this helps.

              -- tom

              Comment


                #8
                I had 'em zip and send me the app and, when I couldn't figure out specifically what had happened, compacted and problem solved.

                Guess I'll just have to call it an unsolved mystery and hope it wasn't due to my ineptitude.

                Thanks to all for your help & patience.

                Bill

                Comment


                  #9
                  Originally posted by Bill
                  I had 'em zip and send me the app and, when I couldn't figure out specifically what had happened, compacted and problem solved.

                  Guess I'll just have to call it an unsolved mystery and hope it wasn't due to my ineptitude.

                  Thanks to all for your help & patience.

                  Bill
                  What you have described would lend itself to Tom's point of


                  c) the report layout uses a specific index that's become corrupt.

                  Since the user is runtime only, compacting the database would only affect the user application by means of packing all tables and thus rebuilding all indexes. This is assuming that you compacted the database before they started using it.

                  The other facet of compacting which packs the data dictionaries would not have made any changes to the user application.
                  There can be only one.

                  Comment

                  Working...
                  X