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

Blank Dates in a Query Within a Query

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

    Blank Dates in a Query Within a Query

    Some of you may recall a post from me (ID# 28499 on 10/5) regarding an expression, part of which invokes a Workdays function (based on one in Peter Wayne's book) that internally runs a query to count holidays between two dates. The problem was that the expression worked fine as a report filter but would not work as a query. None of the help I received cleared the problem, and I feared that A5 couldn't handle running a query containing a function that also runs a query (a query within a query). Most of the error messages were unhelpful (something like "invalid query") in that they pointed to something being wrong with the structure of the query expression when in fact structurally there was nothing wrong. Running debug was similarly unhelpful.

    To make a long story short(er), I finally got one variant of the query to work, whereas another almost identical one would not. When I greatly simplified the non-working query the error message came back with something like "invalid date constant." It turns out that what tripped things up were a few blank dates in the (table) field values used by the Workdays function. THIS WOULD APPEAR TO BE A BUG, unless there is some good reason blank field values should be a problem for an expression used in a query but not be a problem when the same expression is used in a report filter.

    Anyway, at least in my application I can get around the problem by putting a few lines in the Workdays function so it won't trip when it encounters a blank date. My way of substituting a date that does no harm works for my application but may not for others. Suggestions for a better workaround are welcome.

    Ray Lyons

    function Workdays as N(First as D,Last as D,Name_of_Hol_Tbl as C)
    'option strict
    dim dow1 as n
    dim dow2 as n
    dim weekends as n
    dim nholidays as n
    dim offset as n
    dim hol as p 'pointer to the holiday table
    dim ip as p
    dim query.description as c
    dim query.filter as c
    dim query.options as c
    dim query.order as c
    dim fld as p 'pointer to the field in holiday
    dim field_name as c
    dim indx as p
    '**When dates are fields in a table, AND when this function runs within a query,
    '**the blank date fields will result in errors that otherwise do not occur.
    '**So, the next 6 lines (or alternatives) may be needed.
    If Last={}
    Last={01/01/0001} '**Use any date that won't cause a problem
    End If
    If First={}
    First={01/01/0001}
    End If
    on error goto no_holiday_table
    hol=table.open(Name_of_Hol_tbl)
    on error goto 0

    fld=hol.field_get(1) '**Pointer to 1st field in the file
    if fld.type_get()"D" then '**Make sure the 1st field is a date
    workdays=-1
    exit function
    end if
    field_name=fld.name_get() '**name of the 1st field-will be used below

    '**Each offset below either adds or subtracts weekend days to the date
    '**in the date field. Then all you need is the # weekends in between
    dow1=dow(first)
    offset=case(dow1=7,2,dow1=1,1,.t.,0)
    first=first+offset
    dow2=dow(last)
    offset=case(dow2=7,-1,dow2=1,-2,.t.,0)
    last=last+offset
    '**Now just calculate # of weekends and add a fudge factor in the event,
    '**that first - last goes, say, from a Thurs to a Monday
    weekends=int((last-first)/7)+iif(dow(first)>dow(last),1,0)

    '**Now check for holidays
    query.description="holidays between dates"
    query.order=""
    query.options=""
    query.filter="between("+field_name+",first,last)"
    ip=hol.query_create()
    nholidays=ip.records_get()

    '**Finally, just calculate the workdays

    workdays=last-first+1-nholidays-2*weekends
    indx=hol.index_get("holidays between dates")
    indx.drop()
    hol.close()
    exit function

    no_holiday_table:
    on error goto 0
    workdays=-1
    exit function
    end function


    #2
    RE: Blank Dates in a Query Within a Query

    Oops, not home free yet. Now I get the an "invalid date constant" when the one of the variables in Workdays is, say, Datefld+Numfld as in:

    Workdays(Date(),Datefld+Numfld,"holidays")

    where Datefld is a date in a table and Numfld is a numerical field in a table. I also tried just Datefld+15 and the latter as a global calculated field.

    I Also tried:

    jtodate(jdate(Daetfld)+15)

    Same error message in each case, though when I check the expressions in the expression builder they all check out OK.

    A bug or ????

    Ray Lyons

    Comment

    Working...
    X