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
Devcon 2020 Goes Virtual! LEARN MORE >

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

Clarification on Publishing

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    Clarification on Publishing

    Let's say I change a report layout and want to publish the new layout. I assume I have to re-publish the .dbf file related to the report. Will that effect the data in that file on the server? If so, can I just ftp the .dd* files for that .dbf? What is the best protocol for publishing such changes?
    Tommy Thompson
    Thompson Consulting Services
    Beautiful Kentucky Lake, Springville, TN 38256
    [email protected]

    Tags: None
    #2
    Re: Clarification on Publishing

    Don't send the .dbf - that would overwrite the data on your server.

    If the report is based on a table, send the .ddd, .ddm, .ddx.

    If the report is based on a set, send the .set, .sem, .sex.
    -Steve
    sigpic

    Comment

      #3
      Re: Clarification on Publishing

      My suggestion is to always base your report on a set instead of a table even if that's the only use you have for the set. You can publish the set without affecting the data in the tables.

      Some people have even created a "set" with only one table when that's all they needed.

      Pat
      Pat Bremkamp
      MindKicks Consulting

      Comment

        #4
        Re: Clarification on Publishing

        Thanks to both. Good idea Pat.
        Tommy Thompson
        Thompson Consulting Services
        Beautiful Kentucky Lake, Springville, TN 38256
        [email protected]

        Comment

          #5
          Re: Clarification on Publishing

          Originally posted by Pat Bremkamp View Post
          My suggestion is to always base your report on a set instead of a table even if that's the only use you have for the set. You can publish the set without affecting the data in the tables.

          Some people have even created a "set" with only one table when that's all they needed.
          Pat
          Brilliant idea.... It should be done more than less... you just have to remember what is controlling/holding what...

          (It certainly stops the problem of a process wiping out the support files when it runs...)
          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.
          "Make it as simple as possible, but not simpler."
          Albert Einstein

          http://www.iadn.com/images/media/iadn_member.png

          Comment

            #6
            Re: Clarification on Publishing

            Agree, brilliant. Always a pain to update a report on the server. Mostly a pain because of the unknown - did I make any table changes I don't want to publish? Also, when working maintenance with a client, this eliminates having to ask them for the latest table to get the latest report(s) so as not to overwrite with your out-of-date update. Make the report based on a new Set.
            Steve Wood
            See my profile on IADN

            Comment

              #7
              Re: Clarification on Publishing

              My suggestion is to always base your report on a set instead of a table even if that's the only use you have for the set. You can publish the set without affecting the data in the tables.

              Some people have even created a "set" with only one table when that's all they needed
              Yes Pat, I'm one of those people,
              The other advantage is that often later you find that a field from an external field may need to be added, and with a set its inclusion is often quite simple, rather than using ugly Lookup code.

              Comment

              Previous template Next
              Working...
              X