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

Script Failure

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

  • Script Failure

    Can anyone help with this script please? It's out of the Xbasic for Everyone book.
    Marked in Red where it fails.
    Message = "Too many parameters"

    Code:
    'Date Created: 25-Apr-2011 04:55:39 PM
    'Last Updated: 25-Apr-2011 05:24:47 PM
    'Created By  : Ted
    'Updated By  : Ted
    option strict
    dim dstr as c
    dim timestr as c
    dim lstr as c
    dim tstr as c
    dim tbl as p
    dim patient as p
    dim valid as l
    patient=table.current()
    ' overbook attempt
    function overbook as l(dstr as c,timestr as c,sched as p)
    	if sched.records_get()=0 then
    	    overbook=.f.
    		    exit function
    	end if
    	if sched.fetch_find(cdate(ctod(dstr))+str(toseconds(timestr),5))>0 then
    		overbook=.t.
    		exit function
    	else
    		sched.fetch_prev()
    		
    			if .not. sched.fetch_eof() then
    				if ctod(dstr)=sched.date then
    					if toseconds(timestr)<toseconds(sched.time) + (60*sched.length) then
    					overbook=.t.
    			    exit function
    			    end if
    			end if
    		end if
    		sched.fetch_next()
    		if .not. sched.fetch_eof() then
    		    if ctod(dstr)=sched.date then
    		        if toseconds(timestr)+(60*val(lstr))>toseconds(sched.time) then
    		            overbook=.t.
    		            exit function 
    		        end if
    		    end if
    		end if
    	end if
    		end function
    		
    ' User interaction **********************************
    
    dstr=ui_get_date("Appointment Date","Enter Appointment Date:",dtoc(date()))
    if dstr=""then
        end 
        end if
    if ctod(dstr)<date() then
        ui_msg_box("Illegal date","Cannot make appointments in the past",UI_STOP_SYMBOL)
        end 
    end if
    if exist(ctod(dstr),"holiday.dbf","date")then
      	   ui_msg_box("Illegal date","Office Holiday",UI_STOP_SYMBOL)
      	   end   
    end if 
    
    timestr=ui_get_text("Appointment Time","Enter Appointment Time")
    if timestr="" then
        end 
    end if
    if toseconds(timestr)<toseconds("9:00 am").or.toseconds(timestr)>toseconds("5:00 pm")then
        ui_msg_box("Only appointments between 9 and 5",UI_STOP_SYMBOL)
        end
    end if
    if mod(toseconds(timestr),1800)<>0 then
    	ui_msg_box("Wrong Time slot","Appointments on the hour and half hour only",UI_STOP_SYMBOL)
    	end 
    end if	
    lstr=ui_get_number("Appointment Length","Minutes of appointment","30")
    if val(lstr)<0 then
        end 
    end if
    if val(lstr)>60 then
        ui_msg_box("1 Hour","One hour maximum appointment length",UI_STOP_SYMBOL)
        end
    end if
    if val(lstr)>30.and. toseconds(timestr)=toseconds("5:00 pm") then
        ui_msg_box("Quitting Time","No 1 hour appointments at 5.00 pm.",UI_STOP_SYMBOL)
        end 
    end if
    
    tbl=table.open("schedule.dbf",file_rw_shared)
    tbl.index_primary_put("Day_Time")
    
    '*********************************************************************************
    'Check for over booking
    ui_msg_box("data",dstr)
    ui_msg_box("data",timestr)
    ui_msg_box("data",lstr)
    ui_msg_box("data",tbl)
    if overbook(dstr,timestr,lstr,tbl)=.t. then ui_msg_box("Overbooked","Try another time slot",UI_STOP_SYMBOL)  
     tbl.close()
    	end   
    end if
    '*********************************************************************************
    ' No overbook - finish appointment
    tstr=ui_get_text("Comment","Enter Comments")
    on error goto invalid_appt
    valid=.t.
    tbl.enter_begin()
    	tbl.date=ctod(dstr)
    	tbl.time=timestr
    	tbl.length=val(lstr)
    	tbl.comment=left(tstr,40)
    	tbl.patient_id=patient_id
    	close: 
    tbl.enter_end(valid)
    tbl.close()
    end 
    invalid_appt:
    	on error goto 0
    	valid=.f.
    	 ui_msg_box("Invalid day, time or length","Please verify and try again")
    	 resume close
    Last edited by Al Buchholz; 04-26-2011, 06:46 PM. Reason: added code tags.
    Ted Giles
    Example Consulting - UK
    .

    sigpichttp://ec12.example-software.com//
    See our site for Alpha Support, Conversion and Upgrade.

  • #2
    Re: Script Failure

    Ted
    Whilst trying to follow your coding I noticed

    if overbook(dstr,timestr,lstr,tbl)=.t. 'FOUR PARAMETERS

    function overbook as l(dstr as c,timestr as c,sched as p) 'THREE PARAMETERS

    Comment


    • #3
      Re: Script Failure

      Ted,

      long blocks of code are very difficult to read without formatting, indents, etc.

      The message board will preserve your formatting if you surround the code with CODE block markers. Otherwise, everything gets left justified, and difficult to read and understand.

      Please use CODE block markers, or ask for help setting them.

      Thanks.

      Comment


      • #4
        Re: Script Failure

        Along with what Ray found
        if overbook(dstr,timestr,lstr,tbl)=.t. then ui_msg_box("Overbooked","Try another time slot",UI_STOP_SYMBOL)
        maybe should be two lines (for clarity if nothing else!) Assuming that "tbl" is your pointer to the table you are using...
        Code:
        if overbook(dstr,timestr,tbl)=.t. then
            ui_msg_box("Overbooked","Try another time slot",UI_STOP_SYMBOL)
        Last edited by MikeC; 04-26-2011, 07:33 PM.
        Mike
        __________________________________________
        It is only when we forget all our learning that we begin to know.
        It's not what you look at that matters, it's what you see.
        Henry David Thoreau
        __________________________________________



        Comment


        • #5
          Re: Script Failure

          Originally posted by Ray in Capetown View Post
          Ted
          Whilst trying to follow your coding I noticed

          if overbook(dstr,timestr,lstr,tbl)=.t. 'FOUR PARAMETERS

          function overbook as l(dstr as c,timestr as c,sched as p) 'THREE PARAMETERS
          Thanks Ray, it was the lstr that was missing, much obliged - couldn't see the wood for the trees!

          Tom, please advise on what you mean by Code Block Markers. Do you mean Line Numbers, Comments or indents?
          Ted Giles
          Example Consulting - UK
          .

          sigpichttp://ec12.example-software.com//
          See our site for Alpha Support, Conversion and Upgrade.

          Comment


          • #6
            Re: Script Failure

            Originally posted by Ted Giles View Post
            Tom, please advise on what you mean by Code Block Markers. Do you mean Line Numbers, Comments or indents?
            I see that your code formatting has now been nicely preserved. Instead of "block markers" I could have said "tags", but I thought the former was more descriptive. If you still have questions drop me a private message.

            Comment

            Working...
            X