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

Error when try to run report on an encrypted DBF table

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

  • Error when try to run report on an encrypted DBF table

    When I do what the title says, I get an error:

    "error 1143 at line 523"

    The wiki says that error 1143 is "Table is encrypted using a different key."

    Turning encryption off for that table let's the report run without error. Turning encyption on again results in the error again.

    There is no problem with anything else in the app in accessing that table - only reports.

    Has anyone else seen this issue?
    Gary S. Traub, Ph.D.


  • #2
    Re: Error when try to run report on an encrypted DBF table

    bump
    Gary S. Traub, Ph.D.

    Comment


    • #3
      Re: Error when try to run report on an encrypted DBF table

      Not for sure pending on your build release some stuff has changed in the encryption stuff for security reasons. What happens is you create a new dbf save it with crypt NEW key // open it all goes wel but then create a report on that table save with encrypt key //// run the report with the <temp> dbf table?

      Comment


      • #4
        Re: Error when try to run report on an encrypted DBF table

        Hi Eric,

        Thanks for your reply.

        But what do I need to do to get this to work? Any ideas?
        Gary S. Traub, Ph.D.

        Comment


        • #5
          Re: Error when try to run report on an encrypted DBF table

          Can you confirm that as i suggested to try in prev. post does that work incl. the use of a report with encrypted table? Further is the the only table with problems? [encrypt + reports] or are there more?.
          If it's the only table with issues what happens if you copy structure and data to a new dbf encrypt then rename to the orginal and run the report.

          If all your encrypted dbf with reports have problems there two options open / close the dbf for the complete app. Or contact Selwyn I have no direct solution/answer.

          Comment


          • #6
            Re: Error when try to run report on an encrypted DBF table

            Gary - I dealt with this a long time ago and am not certain, but, I think that you can hold the default encryption key as a global variable at the client level to manage this.

            So, at some convenient place (such as a process page after login, or on a page header) you'd want something like this:

            DEFAULT_ENCRYPTION_KEY_SET("YourEncryptionKeyHere")

            I don't think there are any security issues with doing this but would probably explore the possibility of this being exposed as plain text in any case. If that were to be the case, I'd do something with a protected UDF in the AEX, but I think you're fine with just that.
            -Steve
            sigpic

            Comment


            • #7
              Re: Error when try to run report on an encrypted DBF table

              Hi Steve,

              Thanks for the input.

              I already do as you suggest though and it works in v10.5 but not in v12.

              It turns out that turning off the report server eliminates the problem which is good, but I wonder why that is the case.
              Apparently the report server does not like encypted dbf tables.
              Gary S. Traub, Ph.D.

              Comment


              • #8
                Re: Error when try to run report on an encrypted DBF table

                So if it working with the Report Server off then it is a bug as the Report Server is just an engine add/in, ask it to be fixed m2p

                Comment


                • #9
                  Re: Error when try to run report on an encrypted DBF table

                  Gary, I'm having the same issue with my encrypted dbf report. I have used Steve's suggestion in the onDialogExecute and that doesn't work. I don't think I have a report server. Isn't that an add-on?
                  Alpha 5 Version 11
                  AA Build 2999, Build 4269, Current Build
                  DBF's and MySql
                  Desktop, Web on the Desktop and WEB

                  Ron Anusiewicz

                  Comment


                  • #10
                    Re: Error when try to run report on an encrypted DBF table

                    Hi Ron,

                    Go to Project Properties and scroll down until you see Report Server, click on that and then click the box to disable the report server.

                    The Report Server was added to allow use of different cores so that reports don't slow down other processes, but this does not work with DBF tables. SO the problem you are describing disappears when you disable the report server with that one caveat.
                    Gary S. Traub, Ph.D.

                    Comment


                    • #11
                      Re: Error when try to run report on an encrypted DBF table

                      Thanks Gary. That did the trick.
                      Alpha 5 Version 11
                      AA Build 2999, Build 4269, Current Build
                      DBF's and MySql
                      Desktop, Web on the Desktop and WEB

                      Ron Anusiewicz

                      Comment

                      Working...
                      X