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

Filtered report on web, different from Local??

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

    Filtered report on web, different from Local??

    I have created a report that I can call up on the web.

    The report contains 2 sub reports and I have changed the filter for one of the sub reports in the set definitions of the set from which it is derived.

    The desktop report filters as expected.

    The report filters as expected when published to the local webroot.

    Unfortuneately the filter does not operate when published to the WEB.

    I have published all database files to the web and they are identical to those on my development computer.
    Using FTP I have ensured publishing the filis relating to the set and all the tables relating to the set and report but with no success.

    Any suggestions on how to solve this issue.

    Another question.

    If I alter anything to do with a report how do I ensure that I have republished all the information required ton ensure proper display on the web.

    Robert

    #2
    Re: Filtered report on web, different from Local??

    Robert,

    The report definitions are kept in the table files, not in the web pages. Since you stated that this report was for a set, the definition is in the setname.set file. The sets are not normally published when you publish to the web, so that file is probably not being copied to the web host computer, just the tables are published.

    So, to solve your problem, either ftp the set files to the host or add them to the list of database files to publish.

    That also answers your second question. For tables, the report definition is in the tablename.ddd file. So, if you update a report, copy just the .set or the .ddd file to the host. Don't copy the .dbf, or you'll overwrite any data entered through the web.

    After you copy, it would probably be a good idea to redo the indexes on the host. Create the maintenance component if you haven't already.

    Pat
    Pat Bremkamp
    MindKicks Consulting

    Comment


      #3
      Re: Filtered report on web, different from Local??

      Thanks Pat,

      Lots of great advice - good point about the uploading data and overwriting client side data. I would in due course would have done just what you said and caused more heartache.
      What I have been doing is publishing all the set files using ftp but unfortuneately still not altering the report output.

      Reindexing the host files may be the answer. Is there a way of reindexing the host files before I create the maintenanace component.

      Thanks for your advice.

      Regards Robert

      Comment


        #4
        Re: Filtered report on web, different from Local??

        If you have a runtime copy you can install on the server, the runtime desktop can be used to update the tables. You will need to create a "database", or copy the .a* files from your development machine.

        Bill.

        Comment

        Working...
        X