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

Please check my script-- having problems with a shorttime field

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

    Please check my script-- having problems with a shorttime field

    There's one script in the attached database. I remarked out a while statement, that when it's not remarked out, Alpha crashes.

    The while statement reads like this:
    Code:
    h_hour=time("0h",convert_type(hours.time_actual,"T"))
    p_hour=time("0h",convert_type(appt.SCH_TIME,"T"))
    while h_hour = p_hour
    I think it has something to do with the query.order for the appointment table. I originally had hours.time_actual and appt.sch_time as character fields, and the script worked just fine. After changing them to shorttime variables, I haven't been able to get it to work.
    I thought changing the variable type was going to make it more flexible, but I'm thinking I was wrong.
    Before changing the variables, the result table looked something like this:
    Code:
    01:00 am
    . . .
    07:00 am
    07:00 am  07:10 am  detail
    07:00 am  07:30 am  detail2
    08:00 am
    . . .
    Brad Steinfeldt

    #2
    I found my problem. Thanks anyway.

    There's something about posting message. If you work on something something for 3 hours, nothing will click. If I ask a question, I'll find it on my own in 10 minutes.
    Brad Steinfeldt

    Comment


      #3
      It's an uplifting experience, isn't it? ;)

      You do have to share the solution though....

      tks
      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


        #4
        An appointment daily display script

        Happy to explain. Here's what it was doing:
        When it came to the last record of the appt table, sch_time still matched the hours_of_the_day-->sch_time. Since it matched, it kept looping in the embedded while loop and would never kick out.
        To fix it, I added this code:
        Code:
        if prosp.fetch_eof() then p = "30"
        I could have used any number that's not in the 24 hours to avoid the problem, so I used "30". With it kicked out, it continued to write the hours of the day without the appointment detail.
        I added some other if/then statements so that it writes the records in the order I want, and cleans it up.
        I'm sure there are better and prettier code writing, but it works. Here's the code: I'd be flattered if anyone else found value in it:

        Code:
        dim prmpt_title as c 
        dim prmpt_default as c
        dim flag as l 
        dim global which_date as d
        
        prosp = table.open("appointments")          
        hours = table.open("hours_of_the_day")
        flag = .f.
        
        'Prompt for a date and store result in a variable called 'Which_date'.
        prmpt_title = "Print Appointment Schedule for Which Date?"
        prmpt_default = "date()"
        Which_date = ui_get_date_calendar(prmpt_title,prmpt_default)
        	
        query.filter="sch_date={"+which_date+"}"
        query.order= "sch_time"
        query.options="T"
        prosp.query_create()
        hours.fetch_first()
        prosp.fetch_first()
        detail2=table.open("detail2",file_rw_exclusive)
        detail2.zap(.t.)
        'debug(1)
        while .not. hours.fetch_eof()
        	detail2.enter_begin()
        	detail2.sch_hour = hours.Time_actual
        	detail2.enter_end()
        	h = time("0h",convert_type(hours.time_actual,"T"))
        	p = time("0h",convert_type(prosp.SCH_TIME,"T"))
        	while h = p 
        		h = time("0h",convert_type(hours.time_actual,"T"))
        		p = time("0h",convert_type(prosp.SCH_TIME,"T"))
        		if prosp.fetch_eof() then 
        			p = "30"
        		else
        			if .not.flag then
        			    detail2.enter_begin()			'     that match the hour.  remove the remark, and I crash.
        			    detail2.sch_hour = hours.Time_actual
        				detail2.sch_time = prosp.sch_Time
        				detail2.description = prosp.note
        				detail2.enter_end()
        				prosp.fetch_next()
        				flag = .t.
        			else
        				flag = .f.
        			end if
        		end if
        	end while
        	hours.fetch_next()
        end while
        detail2.close()
        'report.preview("report using detail2 as prosp without filtering")
        With this script, you can create a report on the detail2 table so that the hours that don't have detail are also displayed. It makes a daily appointment list much more visual than a regular report, and the user can see what time is open.
        I've sure learn alot with this thing. Much more than I thought I would. I probably wouldn't have started it if I knew how much time I was going to waste.:o
        Er, I mean, how much I was going to learn.
        I've attached a picture of a report I just did.
        Brad Steinfeldt

        Comment


          #5
          Perhaps people will find the Date and Time Conversion Matrix helpful.

          Comment


            #6
            Originally posted by Edward Larrabee
            Perhaps people will find the Date and Time Conversion Matrix helpful.
            Thanks.
            That helps a bunch!
            Brad Steinfeldt

            Comment

            Working...
            X