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

printing report error in upgrade 3369_4093

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

    printing report error in upgrade 3369_4093

    Batchdate is a variable date created from a dialog box in a popup calender to force preview of data for a specific date in the report "carrier report summary"

    The dialog code is as below

    DIM SHARED batchdate as D
    batchdate=date()-1
    DIM SHARED varC_result as C
    ok_button_label = "&OK"
    cancel_button_label = "&Cancel"
    varC_result = ui_dlg_box("Alpha Five",<<%dlg%
    {region}
    Type prompt here:| [%DATE;P=popup.calendar(dtoc(batchdate));I=popup.calendar%.40batchdate!batchdate_*];
    {endregion};
    {line=1,0};
    {region}
    <*15=ok_button_label!OK> <15=cancel_button_label!CANCEL>
    {endregion};
    %dlg%,<<%code%
    if left(a_dlg_button,10) = "batchdate_" then
    if a_dlg_button = "batchdate_killfocus" then
    batchdate = ctod(dtoc(batchdate))
    end if
    a_dlg_button = ""
    end if
    %code%)

    Filter01="batch_date=batchdate"
    :Report.Preview("carrier report summary",Filter01)


    The above code works OK in previous versions of alpha but after the update 3369_4093 alpha reports the filter is incorrect
    Tags: None
    #2
    Re: printing report error in upgrade 3369_4093

    Probably stricter. Filter should be

    Filter01="batch_date= "+s_quote(var->batchdate)
    There can be only one.

    Comment

      #3
      Re: printing report error in upgrade 3369_4093

      in the previous version (3357_4090) i get "Invalid data-type for this operation" when substituting "Filter01="batch_date= "+s_quote(var->batchdate) "

      Comment

        #4
        Re: printing report error in upgrade 3369_4093

        Did you use the line

        "Filter01="batch_date= "+s_quote(var->batchdate) "

        or

        Filter01="batch_date= "+s_quote(var->batchdate)

        If I test in the interactive I see

        Code:
        'your original
DIM SHARED batchdate as D
batchdate=date()-1
DIM SHARED varC_result as C
ok_button_label = "&OK"
cancel_button_label = "&Cancel"
varC_result = ui_dlg_box("Alpha Five",<<%dlg%
{region}
Type prompt here:| [%DATE;P=popup.calendar(dtoc(batchdate));I=popup.calendar%.40batchdate!batchdate_*];
{endregion};
{line=1,0};
{region}
<*15=ok_button_label!OK> <15=cancel_button_label!CANCEL>
{endregion};
%dlg%,<<%code%
if left(a_dlg_button,10) = "batchdate_" then 
if a_dlg_button = "batchdate_killfocus" then 
batchdate = ctod(dtoc(batchdate))
end if 
a_dlg_button = ""
end if
%code%)

Filter01="batch_date = batchdate"
? filter01
= "batch_date = batchdate"

'my suggestion
DIM SHARED batchdate as D
batchdate=date()-1
DIM SHARED varC_result as C
ok_button_label = "&OK"
cancel_button_label = "&Cancel"
varC_result = ui_dlg_box("Alpha Five",<<%dlg%
{region}
Type prompt here:| [%DATE;P=popup.calendar(dtoc(batchdate));I=popup.calendar%.40batchdate!batchdate_*];
{endregion};
{line=1,0};
{region}
<*15=ok_button_label!OK> <15=cancel_button_label!CANCEL>
{endregion};
%dlg%,<<%code%
if left(a_dlg_button,10) = "batchdate_" then 
if a_dlg_button = "batchdate_killfocus" then 
batchdate = ctod(dtoc(batchdate))
end if 
a_dlg_button = ""
end if
%code%)

Filter01="batch_date = "+s_quote(batchdate)
? filter01
= "batch_date = {03/18/2013}"
        There can be only one.

        Comment

          #5
          Re: printing report error in upgrade 3369_4093

          I used the line without the "

          The point I make is that the script has worked perfectly for a number of years but when updateing to 3369_4093 it stopped working. We have reverted to upgrade 3357_4090 and everything is back to normal. The only change we made was the upgrade. This has been tested on more than one computer

          Comment

            #6
            Re: printing report error in upgrade 3369_4093

            Whether it worked or not before......


            Filter01="batch_date = batchdate"
            Is incorrect.

            See Selwyn's reply in this thread (#11).

            http://msgboard.alphasoftware.com/al...pend-operation
            There can be only one.

            Comment

              #7
              Re: printing report error in upgrade 3369_4093

              Well Well

              Seems like alpha has been putting up with my bad coding for some time and decided enough is enough and with help from Stan all is now well

              Cheers mate

              Comment

              Previous template Next
              Working...
              X