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

copy to different adb

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

  • copy to different adb

    I'm not sure if this is even supposed to work, but

    in one adb I made a report, and I said copy to, more, and selected a copy of the adb ( a different adb), and picked the same set the original was made from, and when I said okay, there was a pause and activity indicating it was copying, but it did not copy.

    using 1058
    Cole Custom Programming - Terrell, Texas
    972 524 8714
    martin_w_cole@msn.com

    ____________________
    "A young man who is not liberal has no heart, but an old man who is not conservative has no mind." GB Shaw

  • #2
    RE: copy to different adb

    Martin

    When you are in the target database (.adb) from the control panel press the refresh button. You'll see your report.
    Al Buchholz
    Bookwood Systems, LTD
    Weekly QReportBuilder Webinars Thursday 1 pm CST

    Occam's Razor - KISS
    Normalize till it hurts - De-normalize till it works.
    Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
    When we triage a problem it is much easier to read sample systems than to read a mind.

    Comment


    • #3
      RE: copy to different adb

      thank's Al
      tried that, of course - but no, it ain't there
      I can copy a script, successfully

      also, as a test, I wen back all the way to build 1040 - but it didn't work there either
      Cole Custom Programming - Terrell, Texas
      972 524 8714
      martin_w_cole@msn.com

      ____________________
      "A young man who is not liberal has no heart, but an old man who is not conservative has no mind." GB Shaw

      Comment


      • #4
        RE: copy to different adb

        Martin

        Please post what you have. That should work for a report as well as a script.
        Al Buchholz
        Bookwood Systems, LTD
        Weekly QReportBuilder Webinars Thursday 1 pm CST

        Occam's Razor - KISS
        Normalize till it hurts - De-normalize till it works.
        Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
        When we triage a problem it is much easier to read sample systems than to read a mind.

        Comment


        • #5
          RE: copy to different adb

          Martin

          The report designs are saved in the set data dictionary, which consists of the .set,.sem, sex files and has no connection to the database. If you have the same set with the same tables in a different database, the report should be available in both databases. I don't think you can copy from a set back to the same set.

          Jerry

          Comment


          • #6
            RE: copy to different adb

            Martin

            Are the databases in different directories with the tables and sets completely different files?

            Or is this one directory with 2 databases in that same directory sharing the same tables and sets?

            Or some other arrangement?

            Jerry's point about reports being in the sets and tables is valid. Hence we need to understand more of the situation.

            By telling me that you were able to do it with a script, but not a report, points me to wonder about that report.

            Try duplicating the table/set that the report is based on and copy from the duplicate. Otherwise try another report.
            Al Buchholz
            Bookwood Systems, LTD
            Weekly QReportBuilder Webinars Thursday 1 pm CST

            Occam's Razor - KISS
            Normalize till it hurts - De-normalize till it works.
            Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
            When we triage a problem it is much easier to read sample systems than to read a mind.

            Comment


            • #7
              RE: copy to different adb

              If Jerry is correct about the same named set, duplicate the source set and then copy the report from the duplicated set in the source database to the set in the other data base - I seem to remember this working okay

              Comment


              • #8
                RE: copy to different adb

                I just saw that Al already said this.

                Comment


                • #9
                  RE: copy to different adb

                  Well, I don't think you can copy a layout based on a set from one adb to another.

                  I am working with 2 folders, where 1 is an exact copy of the other.

                  I can copy a form or report based on a single table, but not a set.
                  Cole Custom Programming - Terrell, Texas
                  972 524 8714
                  martin_w_cole@msn.com

                  ____________________
                  "A young man who is not liberal has no heart, but an old man who is not conservative has no mind." GB Shaw

                  Comment


                  • #10
                    RE: copy to different adb

                    Martin, you are not imagining things. I recently discovered the same problem you did.

                    Background:

                    I had two copies of the same database but in different folders. One copy was a "development" copy in which I had created a new report. The second copy was the customer's version in which he had made a few changes since I'd last seen it (a situation I don't enjoy) and I wanted to add my new report without losing any of his changes.

                    Results:

                    I attempted to Copy the new report from my set into the identical set in the second folder. It would not copy. I was selecting the Copy option then scrolling down to the "more> button to navigate to the second folder and select the appropriate set.

                    After about 5 attempts and a reboot, I was about to give up and rebuild it in the new db using cut-and-paste on groups of report objects. However, I got another idea that worked perfectly. By adding the set from the second db to my current db (i.e., two identical sets in one db but each set was in a different folder), I was now able to use the Copy option. The Copy option for sets only seems to work if both sets are in the same database.

                    Comment


                    • #11
                      RE: copy to different adb

                      Thanks Cal. Will try that - in the one adb there is another folder with just a copy of the set, if I understand correctly.

                      PS: a word of extreme caution. Somewhere before 1051, changes to Alpha were made that will cause the following behavior. If you open a 2nd copy of your adb (in a different folder), and put both in design, and then start cutting and pasting, as from one form to another, or maybe scripts for a table in field rules from one to the other, you will wipe out some of the field rules for a table in the first adb, but it won't be one of the tables you are working on. So you are apt not to catch it immediately.

                      This has been quite disheartening for me, as this is one of the ways I have developed for several years using multiple monitors.
                      Cole Custom Programming - Terrell, Texas
                      972 524 8714
                      martin_w_cole@msn.com

                      ____________________
                      "A young man who is not liberal has no heart, but an old man who is not conservative has no mind." GB Shaw

                      Comment


                      • #12
                        RE: copy to different adb

                        Cal

                        I'm doing what Martin is trying to do (and you were trying) all of the time. Without any trouble. Latest build.

                        Even when the report has nothing to do with the table that it is copied to. Just kind of a place holder. Of course it doesn't function very well, but it can be transferred on to another table/set where it does match up well.
                        Al Buchholz
                        Bookwood Systems, LTD
                        Weekly QReportBuilder Webinars Thursday 1 pm CST

                        Occam's Razor - KISS
                        Normalize till it hurts - De-normalize till it works.
                        Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
                        When we triage a problem it is much easier to read sample systems than to read a mind.

                        Comment


                        • #13
                          RE: copy to different adb

                          FWIW: I went back and tested Forms and Browses. They worked fine. Then I tried a report again - no dice. Then I tried other combinations such as:
                          Report in table to same table in 2nd folder - OK.
                          Report in table to same set in 2nd folder - OK.

                          THEN, I had to check the "problem situation" one more time:
                          Report in set to same set in 2nd folder - OK!

                          So, although I'm sure I wasn't imagining things and the first "failed" test was on a simple report as were all the rest of today's tests, it appears that this will take a bit to identify the exact conditions that cause the problem. And, since I have a solution, I don't have the time to undertake a more lengthy test.

                          Comment


                          • #14
                            RE: copy to different adb

                            Al, make a copy of the folder an adb is based on.
                            Make a new report for a set in the fist one.
                            Now copy that report to the second folder/adb to the SAME set - it should fail if it works like mine.
                            Cole Custom Programming - Terrell, Texas
                            972 524 8714
                            martin_w_cole@msn.com

                            ____________________
                            "A young man who is not liberal has no heart, but an old man who is not conservative has no mind." GB Shaw

                            Comment


                            • #15
                              RE: copy to different adb

                              Al, you'll note that I didn't that much testing in the 3 minutes between your response and my last post. I was checking it as you were writing. I had hoped to be able to identify the exact conditions required to duplicate the problem.

                              Comment

                              Working...
                              X