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

Migrating Queries

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

    Migrating Queries

    We seem to be having a problem that we just recently noticed. We have several databases created from one master, each for a different client, in seperate directories, with unique database names.

    When a query is created in one database, it also shows up in the other databases. We are unaware that this ever occurred before.

    Is this normal behavior that we haven't realized. We compact our databases every night.

    Thanks,

    Bill

    #2
    RE: Migrating Queries

    Double check the control panel, tables/sets tab, and look at the full names. Sounds like there is a table or set that is common to all.
    There can be only one.

    Comment


      #3
      RE: Migrating Queries

      Stan,

      Thanks for the thought! I checked & all is ok there. However, I did find, by looking through Windows Explorer, that we have some cross-referenced database files( .alb,.alx,.alm), holdovers apparently from when I copied the database files from the last directory to set-up a new client.

      The directories that have the multiple database files, aren't all of the client directories that we have, and the problem seems to replicate itself through all the client databases, but at least it's a starting point.

      I will try and correct that issue tonight and see where we are.

      Thanks again,

      Bill

      Comment


        #4
        RE: Migrating Queries

        William, if you are talking about 'saved' query operations, I might have an idea for you.

        If it's a real time temporary query list (i.e. query by form), then I couldn't explain what you're seeing.

        -- tom

        Comment


          #5
          RE: Migrating Queries

          After a little more research, we are using version 4, build 95.

          Let me try and explain my situation more clearly. We started with a database for a client & copied all of the files to a new directory. I think what may have happened is that I renamed the .alb, .alm, .alx files.

          On occasions, we run into problems compacting, with an error message that the "previous" database files can't be compacted. As I mentioned in the original post, the "previous" database name(s) continue to appear as files in the new directories. Through Windows Explorer, I deleted the "previous" db names and compacted using version 4.5. Compact went ok. Went back to the version 4 machine and compacted, and the errors reoccurred and the "previous" db named .alb, .alx,. alm files were present in the new directory once again. Perhaps by renaming instead of creating new db files, the data dictionaries still hold remains of the previous database name.

          My next thought is to delete the .alb, .alx, .alm files completely (all of them) and create a new database file, populating it with the tables & sets already in the directory.

          We are planning a version 5 upgrade this summer (I know it's already July) so I prefer not going through ver 4.5 if possible.

          Any ideas?


          Have a good holiday!

          Bill

          Comment


            #6
            RE: Migrating Queries

            There is a patch for version four, without going to version 4.5, that will take you to build 230 - highly recommended. See the technical support area.
            There can be only one.

            Comment

            Working...
            X